Do you happen to run your graylog server on a 32 bit architecture? The
"java.lang.NumberFormatException: Expected an int but was 2259601201" seems
to suggest that it doesn't recognize your 2 billion as an int; and that
number is also slightly over the 32 bits max (for signed integers)
On Monday, February 17, 2014 10:32:36 PM UTC+1, Scotty H wrote:
>
> Upgraded today, it went smoothly.
> Untar both server & web, overwrite stock configs with my rc.2
> configurations (web & server), stop services, update symlinks, start
> services. Done.
> I'm fairly certain I didn't screw it up:
>
>> lrwxrwxrwx 1 root root 28 Feb 17 13:54 graylog2-server
>> -> graylog2-server-0.20.0-rc.3/
>> lrwxrwxrwx 1 root root 35 Feb 17 13:53
>> graylog2-web-interface -> graylog2-web-interface-0.20.0-rc.3/
>
>
> So I was clicking around, and I go to the indices page, the message count
> does not appear. I have approx 1.2TB of log data so far, so I'm expecting
> to see something over 2 billion messages.
> I check the Play web logs that I'm redirecting to a file, and I see this
> entry every time the web interface checks to update the message count
> (every few seconds, of course):
>
> [error] lib.ApiClient - Caught Exception while deserializing JSON request:
>> com.google.gson.JsonSyntaxException: java.lang.NumberFormatException:
>> Expected an int but was 2259601201 at line 1 column 21
>> [error] m.MessagesService - Could not load total message count
>> lib.APIException: API call failed GET http://@
>> 172.16.1.166:12900/count/total returned 200 OK body:
>> {"events":2259601201}
>> at
>> lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:414)
>> ~[graylog2-web-interface.graylog2-web-interface-0.20.0-rc.3.jar:0.20.0-rc.3]
>> at models.MessagesService$2.call(MessagesService.java:90)
>> ~[graylog2-web-interface.graylog2-web-interface-0.20.0-rc.3.jar:0.20.0-rc.3]
>> at models.MessagesService$2.call(MessagesService.java:87)
>> ~[graylog2-web-interface.graylog2-web-interface-0.20.0-rc.3.jar:0.20.0-rc.3]
>> at play.cache.Cache.getOrElse(Cache.java:31)
>> ~[com.typesafe.play.play-cache_2.10-2.2.2-RC1.jar:2.2.2-RC1]
>> at models.MessagesService.total(MessagesService.java:87)
>> ~[graylog2-web-interface.graylog2-web-interface-0.20.0-rc.3.jar:0.20.0-rc.3]
>> at
>> controllers.MessageCountsController.total(MessageCountsController.java:40)
>> [graylog2-web-interface.graylog2-web-interface-0.20.0-rc.3.jar:0.20.0-rc.3]
>
>
>
>
>
> Curl output:
>
>> [root@kirby graylog2-server]# curl -v http://127.0.0.1:12900
>> * About to connect() to 127.0.0.1 port 12900 (#0)
>> * Trying 127.0.0.1... connected
>> * Connected to 127.0.0.1 (127.0.0.1) port 12900 (#0)
>> > GET / HTTP/1.1
>> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
>> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
>> > Host: 127.0.0.1:12900
>> > Accept: */*
>> >
>> < HTTP/1.1 404 Not Found
>> < Transfer-Encoding: chunked
>> <
>> * Connection #0 to host 127.0.0.1 left intact
>> * Closing connection #0
>> [root@kirby graylog2-server]# curl -v http://127.0.0.1:12900/count/total
>> * About to connect() to 127.0.0.1 port 12900 (#0)
>> * Trying 127.0.0.1... connected
>> * Connected to 127.0.0.1 (127.0.0.1) port 12900 (#0)
>> > GET /count/total HTTP/1.1
>> > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/
>> 3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
>> > Host: 127.0.0.1:12900
>> > Accept: */*
>> >
>> < HTTP/1.1 401 Unauthorized
>> < WWW-Authenticate: Basic, Graylog2 Server
>> < Transfer-Encoding: chunked
>> <
>> * Connection #0 to host 127.0.0.1 left intact
>> * Closing connection #0
>> [root@kirby graylog2-server]#
>
>
> Hmmmmmm.
> I can't run graylog2-server in debug mode to see if there's additional
> information because I have SO MUCH data flying at it, there's MANY
> THOUSANDS of lines per second. If it came down to it I could stop traffic
> with iptables if you really need me to.
>
>
--
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/groups/opt_out.
