I recently upgraded netxms and android client to 2.0.4 and unfortunately this is still unresolved. Client locks in some magic state, where not only it doesn't supply any notifications about alarms, but after bringing it to foreground and taping 'alarms' it keeps 'gathering data...' for few moments and then shows 'No items to show...'. Main menu shows 'Connected to server x.x.x.x'. Selecting reconnect fixes this.
On a side note, alert filtering works flawlessly - thank you 
Any idea as to when new version will be available? On a side note, 2.0.3 shows up as 2.0.2 in apps list. Had to uninstall old version to be sure.
Actually it isn't the culprit. Or at least is one of many: same thing happens overnight on my home wifi, and there were no outages.
Thank you. Usability++
No pattern, except maybe for moving through some poor-coverage areas. It just reliably becomes quiet after some time, no alerts, no nothing -- only reconnect helps. And it's not only my problem -- it happens on totally different phone with stock os too. Sending keepalives and reacting to lack of them should be bulletproof.
Android client is losing connection to the server (even on wifi), and carries on as nothing happened. I think it should expect a keepalive packet from the server every [$configurable_interval] seconds and should it miss [$configurable_amount] packets, it should attempt reconnect. This might also possibly affect desktop client; happened to me at least once, but it's not as big a of a problem, since desktop connections tend to be more stable.
Thank you. Just adding a "Ignore" toggle for each severity would be great.
I'd like to only receive critical alerts (about hosts going down etc.) on the android client. Is this possible?
Is this reliably documented somewhere? How can I decide what is the correct netmask? How can I find the device that caused creation of 10.0.0.0/8 subnet with "correct" netmask of /8?
There's still no mention of main, only beta on https://www.netxms.org/download/
2.0.2 is working stable so far. Thanks for you help and repository suggestion.
I'm now running 2.0.2, will see if the problem persists. Should netxms crash again, I'll install debug packages and run netxmsd under gdb again.
Fine. Will do; please fix the website
Sure, I would -- but where do I get them?
I'm using beta repo, as per:
https://www.netxms.org/download/
"Debian packages
Both server and agent packages for wheezy are available in our repository.
deb http://packages.netxms.org/debian wheezy beta"
# dpkg -l | grep netxms
ii netxms-agent:amd64        2.0-RC2-2            amd64    NetXMS agent
ii netxms-base:amd64         2.0-RC2-2            amd64    NetXMS core libraries
ii netxms-dbdrv-pgsql:amd64     2.0-RC2-2            amd64    PostgreSQL driver for netxms-server
ii netxms-dbdrv-sqlite3:amd64    2.0-RC2-2            amd64    SQLite3 driver for netxms-server
ii netxms-server:amd64        2.0-RC2-2            amd64    meta package
Can't find these debug packages anywhere, and just apt-get install doesn't work. 
btw.
Reading symbols from /usr/lib/x86_64-linux-gnu/libnetxms.so.2...(no debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libnxcore.so.2...(no debugging symbols found)...done.
...and it crashed again.
[New Thread 0x7fffa78f8700 (LWP 11125)]
[New Thread 0x7fffa7fff700 (LWP 11130)]
[New Thread 0x7fff9c040700 (LWP 11132)]
[New Thread 0x7fff9fb7b700 (LWP 11139)]
[09-Mar-2016 10:36:52.579] [DEBUG] [CLSN-1] Received message CMD_GET_SERVER_INFO
[09-Mar-2016 10:36:52.579] [DEBUG] [CLSN-1] Server time zone: CET+01CEST
[09-Mar-2016 10:36:52.579] [DEBUG] [CLSN-1] Sending message CMD_REQUEST_COMPLETED
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff9b535700 (LWP 12974)]
0x00007ffff43039f0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0Â 0x00007ffff43039f0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1Â 0x00007ffff68d78b7 in AbstractMessageReceiver::readMessage(unsigned int, MessageReceiverResult*) () from /usr/lib/x86_64-linux-gnu/libnetxms.so.2
#2Â 0x00007ffff7aad0c7 in ClientSession::readThread() () from /usr/lib/x86_64-linux-gnu/libnxcore.so.2
#3Â 0x00007ffff7aad8d9 in ClientSession::readThreadStarter(void*) () from /usr/lib/x86_64-linux-gnu/libnxcore.so.2
#4Â 0x00007ffff5106b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#5Â 0x00007ffff42b930d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#6Â 0x0000000000000000 in ?? ()
Same problem with other commands.
I'm using deb packages.
I kept gdb running after the last crash and tried running rest of commands:
(gdb) frame 1
#1Â 0x00007ffff68d78b7 in AbstractMessageReceiver::readMessage(unsigned int, MessageReceiverResult*) () from /usr/lib/x86_64-linux-gnu/libnetxms.so.2
(gdb) print *this
No symbol table is loaded. Use the "file" command.
(gdb) frame 2
#2Â 0x00007ffff7aad0c7 in ClientSession::readThread() () from /usr/lib/x86_64-linux-gnu/libnxcore.so.2
(gdb) print *this
No symbol table is loaded. Use the "file" command.
I've now restarted, as per your instructions.
Happened sooner than I expected.
[New Thread 0x7fffb4ccc700 (LWP 10037)]
[New Thread 0x7fffaad2d700 (LWP 10067)]
[New Thread 0x7fffaac2c700 (LWP 10095)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffaf777700 (LWP 25348)]
0x00007ffff43039f0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0Â 0x00007ffff43039f0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1Â 0x00007ffff68d78b7 in AbstractMessageReceiver::readMessage(unsigned int, MessageReceiverResult*) () from /usr/lib/x86_64-linux-gnu/libnetxms.so.2
#2Â 0x00007ffff7aad0c7 in ClientSession::readThread() () from /usr/lib/x86_64-linux-gnu/libnxcore.so.2
#3Â 0x00007ffff7aad8d9 in ClientSession::readThreadStarter(void*) () from /usr/lib/x86_64-linux-gnu/libnxcore.so.2
#4Â 0x00007ffff5106b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#5Â 0x00007ffff42b930d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#6Â 0x0000000000000000 in ?? ()
(gdb)
OK, it's running under gdb. What should I do should crash occur? Anything other than bt?
