• Announcements

    • GeorgiTsatsev

      Some Agents Stopped Working   10/30/17

      Dear Domotz Users,    
       
      Symptom
      Please be aware that we are currently experiencing a problem on some Domotz Agents that marks them offline and makes them unreachable. This is primarily affecting the users outside of the US/North American countries.  Domotz is actively working on the resolution of this issue to minimize the impact to you and your customers.
       
      Agents Affected
      QNAP
      Synology
      Raspberry Pi
      Virtual Machine - Debian
      Domotz Boxes   Agents that were affected were running older versions of the Domotz Package (older than 2.1.4).   Agents that had the latest package should not be affected by this issue (2.1.4 or higher).   Root Cause
      Domotz is constantly updating the agent software to improve features and ensure device and network security.   In this instance, Domotz was doing a routine agent upgrade and Agents that had older versions of the package running on the hardware ended up in an offline state.  
       
       
      Resolution
      Domotz is actively working to bring back Domotz Boxes.  We have been able to recover a majority of the Domotz Boxes that had this issue through the Provisioning channel (a parallell channel to the software, mainly used for maintenance and provisioning).   For QNAP, Synology, Raspberry Pi and VM installations, it may be necessary for you to reinstall the latest Domotz software.  
      You can find instructions for updating to the latest version for the Raspberry Pi and VM version might be found on the Domotz Portal (https://portal.domotz.com --> Domotz Software --> Install Instruction for Raspberry Pi and Debian).   The new package (2.1.4) has been published on the QNAP store (available for x86-64 models and ARM x41 models (x31+, x31P, x31P2, x31X, X35) with QTS 4.3.0 and above), and on the Synology store.   We sincerely apologize for any inconvenience caused by this outage. We appreciate the fact that this affects your operations and will do our best to minimize the impact.    Regards,
      The Domotz Support Team
dalem

Agent is online, but showing offline on portal

10 posts in this topic

Hi,

 

I'm new to domotz, I've had it running fine for about a week, when all of a sudden, the portal is showing that my agent went offline.

However, the web configuration page for the agent is showing as online. The portal is still updating the status of the devices on the network though (which would indicate the agent is actually working)

 

I'm using the Debian based agent on Ubuntu server 16.04.1, I've tried restarting the domotz service, and also rebooted the Ubuntu server which did not solve the issue. 

Thanks.

0

Share this post


Link to post
Share on other sites

mhm... quite strange. Can you perform a "ps -ef | grep domotz" on the Ubuntu Server, to check the status?

 

Eventually, have a look at the /var/log/domotz/ folder for relevant logs. 

0

Share this post


Link to post
Share on other sites
dale@ubuntu-server:~$ ps -ef | grep domotz
root      4012     1  0 21:35 ?        00:00:00 /opt/domotz/bin/domotz_node /opt/domotz/lib/node_modules/forever/bin/monitor /opt/domotz/bin/domotz_listener
root      4029     1  0 21:35 ?        00:00:00 domotz_zabbix_agentd -c /opt/domotz/etc/zabbix_agentd.conf
root      4036  4029  0 21:35 ?        00:00:01 domotz_zabbix_agentd: collector [idle 1 sec]
root      4037  4029  0 21:35 ?        00:00:00 domotz_zabbix_agentd: listener #1 [waiting for connection]
root      4038  4029  0 21:35 ?        00:00:00 domotz_zabbix_agentd: active checks #1 [idle 1 sec]
root      4051  4012  0 21:35 ?        00:00:26 /opt/domotz/bin/domotz_node /opt/domotz/bin/domotz_listener
root      4125     1  0 21:35 ?        00:00:00 domotz_zabbix_proxy -c /opt/domotz/etc/zabbix_proxy.conf
root      4127  4125  0 21:35 ?        00:00:25 domotz_zabbix_proxy: configuration syncer [loading configuration]
root      4128  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: heartbeat sender [sending heartbeat message success in 0.880253 sec, idle 59 sec]
root      4129  4125  0 21:35 ?        00:00:11 domotz_zabbix_proxy: data sender [sent 0 values in 0.002067 sec, idle 1 sec]
root      4130  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: poller #1 [got 0 values in 0.000008 sec, idle 5 sec]
root      4131  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: unreachable poller #1 [got 1 values in 60.007346 sec, getting values]
root      4132  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: trapper #1 [processed data in 0.000432 sec, waiting for connection]
root      4133  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: trapper #2 [processed data in 0.000456 sec, waiting for connection]
root      4134  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: trapper #3 [processed data in 0.000398 sec, waiting for connection]
root      4135  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: housekeeper [deleted 2677 records in 0.011807 sec, idle 3600 sec]
root      4136  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: discoverer #1 [processed 0 rules in 0.000251 sec, idle 60 sec]
root      4137  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: history syncer #1 [synced 0 items in 0.000002 sec, idle 5 sec]
root      4138  4125  0 21:35 ?        00:00:00 domotz_zabbix_proxy: self-monitoring [processed data in 0.000003 sec, idle 1 sec]
dale      8777  8764  0 23:53 pts/0    00:00:00 grep --color=auto domotz

I had a look through the logs in /var/log/domotz but nothing really stands out. What should I be looking for? There is a lot of entries in the logs there.

Thanks,

0

Share this post


Link to post
Share on other sites

I've reset the agent in the portal, removed the package from the Ubuntu server, and then reinstalled the .deb package but it's still showing up as offline.

0

Share this post


Link to post
Share on other sites

Any changes at firewall level?

0

Share this post


Link to post
Share on other sites

No, I haven't changed anything on my firewall. 
The installation and activation all works fine, however.

0

Share this post


Link to post
Share on other sites

You are not alone.. I have exactly the same issue and I've had my PI for 4 days... Done the above and see no apparent issues.  Help please.

0

Share this post


Link to post
Share on other sites

Looks like the issue has been fixed on the server-side. Thanks guys!

0

Share this post


Link to post
Share on other sites

My Dallas agent was working all day yesterday and stopped at around 5p. This morning I checked and the network port is fine and the device has power. I restarted, no change in status.

0

Share this post


Link to post
Share on other sites
5 hours ago, rfrymire said:

My Dallas agent was working all day yesterday and stopped at around 5p. This morning I checked and the network port is fine and the device has power. I restarted, no change in status.

 

The agent should be back online. Just saw into the support ticket.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now