Gladys unavailable after reboot

Configuration
21

You should edit your post as all your connection keys are in plain text…

22

All the values are already truncated :wink:

23

Okay. That’s good, I read your message too quickly.

24

I don’t see any MQTT-related variables.

25

That’s it, that’s why I wrote to Pierre-Gilles that he would be disappointed…

26

Where does the value m14cloudmqtt.com come from?

27

Can you run a ‹ docker logs › again to see if the error is still the same?

28 
> gladys-server@ start:prod /src/server
 > cross-env NODE_ENV=production node index.js
 
 Initialising OpenZWave 1.6.1051 binary addon for Node.JS.
 	OpenZWave Security API is ENABLED
 	ZWave device db    : /usr/local/etc/openzwave
 	User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
 	Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
 2020-09-13T20:16:20+0200 <info> index.js:20 (Object.start) Starting Open Weather service
 2020-09-13T20:16:20+0200 <info> index.js:19 (Object.start) Starting telegram service
 2020-09-13T20:16:20+0200 <info> index.js:13 (Object.start) Starting usb service
 2020-09-13T20:16:20+0200 <info> index.js:16 (Object.start) Starting zwave service
 2020-09-13T20:16:29+0200 <info> service.start.js:16 (Service.start) Service telegram is not configured, so it was not started.
 2020-09-13T20:16:37+0200 <warn> connect.js:50 (MqttClient.<anonymous>) Error while connecting to MQTT - Error: getaddrinfo ENOTFOUND m14cloudmqtt.com
 events.js:292
       throw er; // Unhandled 'error' event
       ^
 
 Error: getaddrinfo ENOTFOUND m14cloudmqtt.com
     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:66:26)
 Emitted 'error' event on MqttClient instance at:
     at TLSSocket.streamErrorHandler (/src/server/services/mqtt/node_modules/mqtt/lib/client.js:333:12)
     at TLSSocket.emit (events.js:327:22)
     at emitErrorNT (internal/streams/destroy.js:92:8)
     at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
   errno: 'ENOTFOUND',
   code: 'ENOTFOUND',
   syscall: 'getaddrinfo',
   hostname: 'm14cloudmqtt.com'
 }
 npm ERR! code ELIFECYCLE
 npm ERR! errno 1
 npm ERR! gladys-server@ start:prod: `cross-env NODE_ENV=production node index.js`
 npm ERR! Exit status 1
 npm ERR! 
 npm ERR! Failed at the gladys-server@ start:prod script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 
 npm ERR! A complete log of this run can be found in:
 npm ERR!     /root/.npm/_logs/2020-09-13T20_16_37_949Z-debug.log
29

Hello everyone,

I think I’m going to end up reinstalling. I continued to search a bit and I didn’t find anything relevant to solve my problem.

30

If you go for a reinstall, really make sure to get the latest Raspbian image from Gladys’ website :slight_smile:

31

I already did that 3 months ago…
But with my 1.2 Mbps connection, it’s still really slow…

32

@pierre-gilles
On September 10th, you said the bug was critical. Before wiping everything on the SD, can you confirm that the bug is not critical?

33

Given that I couldn’t reproduce your bug, I think your installation was just not up to date :slight_smile:

I think it’s better to reinstall at this stage. Keep us updated on the reinstallation!

34

Fabichou, shouldn’t the MQTT server address be m14.cloudmqtt.com instead of m14cloudmqtt.com?

35

Yes, there is an error in the URL, but it is not stored in the Gladys database… it’s really strange. Since then, it can no longer start.

36

Hello everyone
I just reinstalled my SD card with the latest version of Galdys.
Then I connected my Gladys Plus account and I wanted to restore a backup from 2 months ago, well before my issue…
But I still have the same behavior… It keeps rebooting…
Are all my backups corrupted??
I’m a bit tired of trying 3 backups and always failing…

37

Oh no :confused: really…

There must be something wrong with your installation, would you mind sending me (privately) your Gladys DB file so I can run it on my side? We’ll see right away where the problem comes from.

The Gladys SQLite DB is located on the Pi at:

/var/lib/gladysassistant/gladys-production.db

You just have to download this file to your PC (You can use tools like FileZilla/Cyberduck), and then send me the file in a private message, if you don’t mind.

I rarely ask for this kind of private information but given the problems you’re having, it seems to be the last resort to understand what’s going on…

I understand, it’s frustrating! I thought on my side that you had a bug due to an old version of Gladys (uncaught MQTT error), but apparently that’s not the case, my diagnosis was not correct. Your local DB should give me more clues, I’ll run your instance on my side.

38

Hello
Thank you Pierre-Gilles.
It’s been sent to your email.

39

Thanks @Fabichou! I’ll check it out.

40

@Fabichou

After investigating the 2 DBs you sent me:

  1. The DB from September 11 has no apparent issues. It runs very well on my end, no crashes, and I don’t see anything in the DB that relates to MQTT. I don’t understand how you can have an error « Error: getaddrinfo ENOTFOUND m14cloudmqtt.com » if there’s nothing related to MQTT on the DB side…

  2. The second DB, after restoration, is empty. That’s strange! Is your restoration process running normally?

Given this information, I think the MQTT error we saw wasn’t the one causing your crash; there must have been something else in the logs that you might have missed…

Would you be available for a call during the day/evening to explain what you’re doing? It will probably be easier to understand each other.