Gargam3L0 had version FireMotD v7.05.170509 and for some reason the update within openhabian-config didn’t work. This old version didn’t show the IP even with a manual FireMotD -S. So I guess it’s a mixture of both - old version and network not up during boot.
PS: @mstormi please correct me but afaik older openhabian installations don‘t have FireMotD running as a service?
Right, this was changed some time ago. IIRC it was triggered from cron before. You can remove or keep the cronjob if you still have it.
Right, /etc/cron.d/firemotd:
# FireMotD system updates check (randomly execute between 0:00:00 and 5:59:59)
0 0 * * * root perl -e 'sleep int(rand(21600))' && /bin/bash /usr/local/bin/FireMotD -S -D all &> /dev/nullDoesn’t seem to work for me. After reboot there’s still the “unable to parse ip” message.
Can you please run the following command and post the output?
sudo systemctl status firemotd.service
Also please post the content of file:
/etc/systemd/system/firemotd.service
**output of **
sudo systemctl status firemotd.service
firemotd.service - Periodic FireMotD stats regeneration
Loaded: loaded (/etc/systemd/system/firemotd.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2020-10-30 16:09:45 CET; 38min ago
Main PID: 536 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/firemotd.service
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/buster/InRelease Temporary failure resolvi
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/InRelease Temporary failure resolving ’
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease Temporary failure resolving 'r
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Failed to fetch https://deb.nodesource.com/node_10.x/dists/buster/InRelease Temporary failure resolving ’
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Failed to fetch https://dl.bintray.com/openhab/apt-repo2/dists/stable/InRelease Temporary failure resolvi
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease Temporary failure resolving
Oct 30 16:09:39 openHABianDevice FireMotD[536]: W: Some index files failed to download. They have been ignored, or old ones used instead.
Oct 30 16:09:45 openHABianDevice systemd[1]: Started Periodic FireMotD stats regeneration.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Content of file:
/etc/systemd/system/firemotd.service
[Unit]
Description=Periodic FireMotD stats regeneration
After=network.target network-online.target
[Service]
Type=oneshot
User=root
Group=root
RemainAfterExit=yes
ExecStart=/usr/local/bin/FireMotD -S -D all &> /dev/null
[Install]
WantedBy=multi-user.target
Please try:
sudo systemctl restart firemotd.service
and then check again with:
sudo systemctl status firemotd.service
If the error still occurs, please also post the output of:
sudo systemctl status firemotd.timer
Oh, and did you run the 2 commands @mstormi mentioned (after editing the firemotd.service-file)?
sudo systemctl daemon-reload
sudo systemctl enable --now firemotd.timer
Yes, i did run
sudo systemctl daemon-reload
sudo systemctl enable --now firemotd.timer
sudo systemctl restart firemotd.service
resolves the problem, but after a reboot there’s the same errors again.
Output of “sudo systemctl status firemotd.timer” :
firemotd.timer - Daily generation of FireMotD stats
Loaded: loaded (/etc/systemd/system/firemotd.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Fri 2020-10-30 16:58:57 CET; 5min ago
Trigger: Sat 2020-10-31 02:32:30 CET; 9h left
Oct 30 16:58:57 openHABianDevice systemd[1]: Started Daily generation of FireMotD stats.
And after a reboot, what is the output of:
sudo systemctl status firemotd.service
firemotd.service - Periodic FireMotD stats regeneration
Loaded: loaded (/etc/systemd/system/firemotd.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2020-10-30 17:05:56 CET; 9min ago
Process: 497 ExecStart=/usr/local/bin/FireMotD -S -D all &> /dev/null (code=exited, status=0/SUCCESS)
Main PID: 497 (code=exited, status=0/SUCCESS)
Oct 30 17:05:34 openHABianDevice systemd[1]: Starting Periodic FireMotD stats regeneration…
Oct 30 17:05:36 openHABianDevice FireMotD[497]: RTNETLINK answers: Network is unreachable
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/buster/InRelease Temporary failure resolvi
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/InRelease Temporary failure resolving ’
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease Temporary failure resolving 'r
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Failed to fetch https://deb.nodesource.com/node_10.x/dists/buster/InRelease Temporary failure resolving ’
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Failed to fetch https://dl.bintray.com/openhab/apt-repo2/dists/stable/InRelease Temporary failure resolvi
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease Temporary failure resolving
Oct 30 17:05:50 openHABianDevice FireMotD[497]: W: Some index files failed to download. They have been ignored, or old ones used instead.
Oct 30 17:05:56 openHABianDevice systemd[1]: Started Periodic FireMotD stats regeneration.
Could this be related?
That’s strange! So during reboot it seems that the network connection can not be established even if you have added:
After=network.target network-online.target
exactly. Content of firemotd.service:
[Unit]
Description=Periodic FireMotD stats regeneration
After=network.target network-online.target
[Service]
Type=oneshot
User=root
Group=root
RemainAfterExit=yes
ExecStart=/usr/local/bin/FireMotD -S -D all &> /dev/null
[Install]
WantedBy=multi-user.target
I noticed, although it was resolved, I don’t know if it is related, that after updating to 2.5.10
the IP is shown in the login welcome message only after a couple of minutes from system reboot, not immediately.
[EDIT]
I take that back, it does not work anymore.
[18:44:58] openhabian@openHABianPi:~$ sudo systemctl status firemotd.service
● firemotd.service - Periodic FireMotD stats regeneration
Loaded: loaded (/etc/systemd/system/firemotd.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2020-10-30 12:11:13 IST; 6h ago
Process: 342 ExecStart=/usr/local/bin/FireMotD -S -D all &> /dev/null (code=exited, status=0/SUCCESS)
Main PID: 342 (code=exited, status=0/SUCCESS)
Oct 30 12:11:03 openHABianPi FireMotD[342]: RTNETLINK answers: Network is unreachable
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/buster/InRelease Temporary failure resolving 'raspbian.
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch https://repos.influxdata.com/debian/dists/jessie/InRelease Temporary failure resolving 'repos.influxda
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch https://repo.mosquitto.org/debian/dists/buster/InRelease Temporary failure resolving 'repo.mosquitto.o
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch https://deb.nodesource.com/node_10.x/dists/jessie/InRelease Temporary failure resolving 'deb.nodesourc
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch https://dl.bintray.com/openhab/apt-repo2/dists/stable/InRelease Temporary failure resolving 'dl.bintra
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease Temporary failure resolving 'archive.rasp
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Failed to fetch http://repos.azulsystems.com/debian/dists/stable/InRelease Temporary failure resolving 'repos.azulsyst
Oct 30 12:11:09 openHABianPi FireMotD[342]: W: Some index files failed to download. They have been ignored, or old ones used instead.
Oct 30 12:11:13 openHABianPi systemd[1]: Started Periodic FireMotD stats regeneration.
[18:43:41] openhabian@openHABianPi:~$ sudo systemctl status firemotd.timer
● firemotd.timer - Daily generation of FireMotD stats
Loaded: loaded (/etc/systemd/system/firemotd.timer; disabled; vendor preset: enabled)
Active: inactive (dead)
Trigger: n/aRun again openhabian-config with apply imporovments “FireMotD” option.
Now SSH login shows IP.
Did not try a reboot. Maybe it will return.
No since there’s no packages that are upgraded or installed.
remove that line, too
Right or do that. That only works since a couple of minutes because I added the fix to the repo.
Note you must be on master branch.
Doesnt seem to make a difference
I’m having the same problem but I don’t have a firemotd.service file or anything close to that.
If this doesn’t cause any problems I’m not worried about it. But after the upgrade I’m no longer able to connect to the MQTT server using MQTT.fx to test my system.
Read more carefully.
You should upgrade to latest openHABian then this problem (as the title says) should be gone.
Don’t mix other topics into this. Any other problem is obviously unrelated and just related to your openHAB upgrade .