Great!

I'll open an issue to improve server side logging for this issue.

Best,
Kay
On May 26, 2014 3:03 PM, <[email protected]> wrote:

> Yes, you are right. That was the problem. After creating stream and adding
> permissions for a regular user it works as expected.
> Thank you.
>
>
> W dniu poniedziałek, 26 maja 2014 14:01:08 UTC+2 użytkownik Kay Röpke
> napisał:
>>
>> I just realize that maybe the problem with the dashboard is configured
>> with a search result that the user would not be allowed to see.
>> Read-only users can only search in streams, but not over all results,
>> currently.
>>
>> On Mon, May 26, 2014 at 1:59 PM, Kay Röpke <[email protected]> wrote:
>> > But both of these requests are for different URLs than dashboards.
>> > One is a non-stream search and the second one is the threaddump view.
>> >
>> > Both of which aren't available for read-only users.
>> > Are you sure the dashboards do not work?
>> >
>> > Best,
>> > Kay
>> >
>> > On Mon, May 26, 2014 at 10:40 AM,  <[email protected]> wrote:
>> >> I did it on the 0.20.2-rc1 and I tried with many users. Still the same
>> >> error. I've got the same issue on the other server. Both machines with
>> >> Ubuntu 12.04.
>> >>
>> >> And I have the same error when I try to open ThreadDump:
>> >>
>> >>
>> >> Oh no, something went wrong!
>> >>
>> >> (You caused a lib.APIException. API call failed GET
>> >> http://@192.168.56.101:12900/system/threaddump returned 403 Forbidden
>> body:
>> >> )
>> >>
>> >> Reason: Could not fetch system information. We expected HTTP 200, but
>> got a
>> >> HTTP 403.
>> >>
>> >>
>> >> Stacktrace
>> >>
>> >> lib.ApiClientImpl$ApiRequestBuilder#execute (ApiClientImpl.java:372)
>> >> models.Node#getThreadDump (Node.java:186)
>> >> controllers.NodesController#threadDump (NodesController.java:106)
>> >> Routes$$anonfun$routes$1$$anonfun$applyOrElse$40$$anonfun$apply$118#apply
>>
>> >> (routes_routing.scala:957)
>> >> Routes$$anonfun$routes$1$$anonfun$applyOrElse$40$$anonfun$apply$118#apply
>>
>> >> (routes_routing.scala:957)
>> >> play.core.Router$HandlerInvoker$$anon$7$$anon$2#invocation
>> >> (Router.scala:183)
>> >> play.core.Router$Routes$$anon$1#invocation (Router.scala:377)
>> >> play.core.j.JavaAction$$anon$1#call (JavaAction.scala:56)
>> >> play.GlobalSettings$1#call (GlobalSettings.java:64)
>> >> play.mvc.Security$AuthenticatedAction#call (Security.java:45)
>> >> play.core.j.JavaAction$$anon$3#apply (JavaAction.scala:91)
>> >> play.core.j.JavaAction$$anon$3#apply (JavaAction.scala:90)
>> >> play.core.j.FPromiseHelper$$anonfun$flatMap$1#apply
>> >> (FPromiseHelper.scala:82)
>> >> play.core.j.FPromiseHelper$$anonfun$flatMap$1#apply
>> >> (FPromiseHelper.scala:82)
>> >> scala.concurrent.Future$$anonfun$flatMap$1#apply (Future.scala:251)
>> >> scala.concurrent.Future$$anonfun$flatMap$1#apply (Future.scala:249)
>> >> scala.concurrent.impl.CallbackRunnable#run (Promise.scala:32)
>> >> play.core.j.HttpExecutionContext$$anon$2#run
>> (HttpExecutionContext.scala:37)
>> >> akka.dispatch.TaskInvocation#run (AbstractDispatcher.scala:42)
>> >> akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask#exec
>> >> (AbstractDispatcher.scala:386)
>> >> scala.concurrent.forkjoin.ForkJoinTask#doExec (ForkJoinTask.java:260)
>> >> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue#runTask
>> >> (ForkJoinPool.java:1339)
>> >> scala.concurrent.forkjoin.ForkJoinPool#runWorker
>> (ForkJoinPool.java:1979)
>> >> scala.concurrent.forkjoin.ForkJoinWorkerThread#run
>> >> (ForkJoinWorkerThread.java:107)
>> >>
>> >>
>> >>
>> >>
>> >> W dniu piątek, 23 maja 2014 13:11:44 UTC+2 użytkownik Kay Röpke
>> napisał:
>> >>>
>> >>> I'm sorry, I just tried this again with the last development version
>> >>> (unchanged to 0.20.2-rc1 in this respect) and it works as expected.
>> >>> Could you please remove the permissions for that user, add them back
>> (save
>> >>> in between, of course) and try again?
>> >>>
>> >>> Maybe something related to how the permissions have been saved is
>> broken?
>> >>>
>> >>> Thanks,
>> >>> Kay
>> >>>
>> >>> On Friday, May 23, 2014 11:37:55 AM UTC+2, [email protected]:
>> >>>>
>> >>>> Latest 0.20.2-rc.1 version has the same issue.
>> >>>>
>> >>>> W dniu środa, 21 maja 2014 15:13:30 UTC+2 użytkownik
>> [email protected]
>> >>>> napisał:
>> >>>>>
>> >>>>> Unfortunately no. I will try to upgrade to the latest version and
>> see
>> >>>>> what happen.
>> >>>>>
>> >>>>> W dniu piątek, 16 maja 2014 23:12:16 UTC+2 użytkownik Tyler Bell
>> >>>>> napisał:
>> >>>>>>
>> >>>>>> Did you ever discover the cause? I'm seeing this exact issue.
>> >>>>>>
>> >>>>>> On Friday, April 25, 2014 3:42:50 AM UTC-6, [email protected]:
>> >>>>>>>
>> >>>>>>> I've got an error if I am trying to open dashboard as reader
>> user.
>> >>>>>>> User has permissions to read and edit dashboard.
>> >>>>>>>
>> >>>>>>> "Oh no, something went wrong!
>> >>>>>>>
>> >>>>>>> (You caused a lib.APIException. API call failed GET
>> >>>>>>> http://@10.0.3.1:12900/search/universal/relative?range=3600&;
>> range_type=relative&query=*&limit=100&offset=0&filter=*&
>> sort=timestamp:desc
>> >>>>>>> returned 403 Forbidden body: )
>> >>>>>>>
>> >>>>>>> Reason: There was a problem with your search. We expected HTTP
>> 200,
>> >>>>>>> but got a HTTP 403."
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Graylog version is 0.20.1.
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups
>> >> "graylog2" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> an
>> >> email to [email protected].
>> >> For more options, visit https://groups.google.com/d/optout.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "graylog2" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to