Yogesh Bhanu
2020-Jun-26 13:14 UTC
[Nut-upsuser] reboot of nut managment node resets Tripplite SMX1000LCD
Hi Roger et.al, The shutdown /reset of UPS is near instantaneous after rpi reboots or switches off. FWIW -- It looks like something is off with Ubuntu 20.04 -- I tried with raspbian and arch linux using the same nut configuration on the same hardware and the UPS does not reset. I have repurposed an old rpi2 to act as a nut server. Thanks Roger. Yogesh On Mon, Jun 22, 2020 at 11:33 AM Roger Price <roger at rogerprice.org> wrote:> > On Mon, 22 Jun 2020, Yogesh Bhanu wrote: > > > I'm not sure if it is a bug or a feature. > > > > I'm running Ubuntu 20.04 on my RPi4 which connects to the UPS over USB. > > I have noticed whenever I reboot my RPi4. It resets the UPS ( I can > > hear the relay) -- Powerloss. > > Any pointers to disable this annoying bug / feature. > > It looks as if the shutdown part of the reboot is issuing a "delayed UPS > shutdown". You should be able to see this in the log. The UPS will then turn > off it's power outlets say 20 seconds later when the RPi4 has already restarted. > > Ways to avoid this: > > 1. Remove wall power and wait to hear the "clunk" of the relay. Then restore > wall power. > > 2. Stop nut.server before rebooting the RPi4. This could happen in a script. > > Roger > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Roger Price
2020-Jun-26 13:58 UTC
[Nut-upsuser] reboot of nut managment node resets Tripplite SMX1000LCD
On Fri, 26 Jun 2020, Yogesh Bhanu wrote:> Hi Roger et.al, > > The shutdown /reset of UPS is near instantaneous after rpi reboots or > switches off. > FWIW -- It looks like something is off with Ubuntu 20.04 -- I tried > with raspbian and arch linux using the same nut configuration on the > same hardware and the UPS does not reset.Could you describe the exact procedure you use to reboot. The commands you use, the systemd service unit involved, and the relevant entries in the system log. Roger
Yogesh Bhanu
2020-Jun-27 12:56 UTC
[Nut-upsuser] reboot of nut managment node resets Tripplite SMX1000LCD
Hi Roger et.al, Following messages are logged by journalctl when powering off. --snip-- Jun 25 11:26:32 fourpi01 containerd[1326]: time="2020-06-25T11:26:32.638781892+10:00" level=info msg="Stop CRI service" Jun 25 11:26:32 fourpi01 systemd[1]: Stopping Network UPS Tools - power device driver controller... Jun 25 11:26:32 fourpi01 upsdrvctl[258149]: Network UPS Tools - UPS driver controller 2.7.4 Jun 25 11:26:32 fourpi01 usbhid-ups[1472]: Signal 15: exiting Jun 25 11:26:32 fourpi01 systemd[1]: Starting Show Plymouth Reboot Screen... Jun 25 11:26:32 fourpi01 systemd[1]: Stopping User Runtime Directory /run/user/1001... Jun 25 11:26:32 fourpi01 systemd[1]: Stopping User Manager for UID 997... Jun 25 11:26:32 fourpi01 systemd[1547]: Stopped target Main User Target. Jun 25 11:26:32 fourpi01 systemd[1547]: Stopped target Basic System. Jun 25 11:26:32 fourpi01 systemd[1547]: Stopped target Paths. Jun 25 11:26:32 fourpi01 systemd[1547]: Stopped target Sockets. Jun 25 11:26:32 fourpi01 systemd[1547]: Stopped target Timers. Jun 25 11:26:32 fourpi01 systemd[1547]: dbus.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed D-Bus User Message Bus Socket. Jun 25 11:26:32 fourpi01 systemd[1547]: dirmngr.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed GnuPG network certificate management daemon. Jun 25 11:26:32 fourpi01 systemd[1547]: gpg-agent-browser.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Jun 25 11:26:32 fourpi01 systemd[1547]: gpg-agent-extra.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Jun 25 11:26:32 fourpi01 systemd[1547]: gpg-agent-ssh.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed GnuPG cryptographic agent (ssh-agent emulation). Jun 25 11:26:32 fourpi01 systemd[1]: nut-driver.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: gpg-agent.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed GnuPG cryptographic agent and passphrase cache. Jun 25 11:26:32 fourpi01 systemd[1547]: pk-debconf-helper.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed debconf communication socket. Jun 25 11:26:32 fourpi01 systemd[1547]: snapd.session-agent.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Closed REST API socket for snapd user session agent. Jun 25 11:26:32 fourpi01 systemd[1547]: Reached target Shutdown. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped Network UPS Tools - power device driver controller. Jun 25 11:26:32 fourpi01 systemd[1547]: systemd-exit.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1547]: Finished Exit the Session. Jun 25 11:26:32 fourpi01 systemd[1547]: Reached target Exit the Session. Jun 25 11:26:32 fourpi01 systemd[1]: Received SIGRTMIN+20 from PID 258153 (plymouthd). Jun 25 11:26:32 fourpi01 systemd[1]: containerd.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped containerd container runtime. Jun 25 11:26:32 fourpi01 systemd[1548]: pam_unix(systemd-user:session): session closed for user pihole Jun 25 11:26:32 fourpi01 systemd[257521]: run-user-1001.mount: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: run-user-1001.mount: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Unmounted /run/user/1001. Jun 25 11:26:32 fourpi01 apport[258078]: * Stopping automatic crash report generation: apport Jun 25 11:26:32 fourpi01 systemd[1]: user at 997.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped User Manager for UID 997. Jun 25 11:26:32 fourpi01 systemd[1]: user-runtime-dir at 1001.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped User Runtime Directory /run/user/1001. Jun 25 11:26:32 fourpi01 apport[258078]: ...done. Jun 25 11:26:32 fourpi01 systemd[1]: apport.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped LSB: automatic crash report generation. Jun 25 11:26:32 fourpi01 systemd[1]: Started Show Plymouth Reboot Screen. Jun 25 11:26:32 fourpi01 systemd[1]: Removed slice User Slice of UID 1001. Jun 25 11:26:32 fourpi01 systemd[1]: Stopping User Runtime Directory /run/user/997... Jun 25 11:26:32 fourpi01 systemd[257521]: run-user-997.mount: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: run-user-997.mount: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopping User Manager for UID 1002... Jun 25 11:26:32 fourpi01 systemd[257521]: Stopped target Main User Target. Jun 25 11:26:32 fourpi01 systemd[257521]: Stopped target Basic System. Jun 25 11:26:32 fourpi01 systemd[257521]: Stopped target Paths. Jun 25 11:26:32 fourpi01 systemd[257521]: Stopped target Sockets. Jun 25 11:26:32 fourpi01 systemd[257521]: Stopped target Timers. Jun 25 11:26:32 fourpi01 systemd[257521]: dbus.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd-logind[1270]: Session 867 logged out. Waiting for processes to exit. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed D-Bus User Message Bus Socket. Jun 25 11:26:32 fourpi01 systemd[257521]: dirmngr.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed GnuPG network certificate management daemon. Jun 25 11:26:32 fourpi01 systemd[257521]: gpg-agent-browser.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Jun 25 11:26:32 fourpi01 systemd[257521]: gpg-agent-extra.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Jun 25 11:26:32 fourpi01 systemd[257521]: gpg-agent-ssh.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed GnuPG cryptographic agent (ssh-agent emulation). Jun 25 11:26:32 fourpi01 systemd[257521]: gpg-agent.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed GnuPG cryptographic agent and passphrase cache. Jun 25 11:26:32 fourpi01 systemd[257521]: pk-debconf-helper.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed debconf communication socket. Jun 25 11:26:32 fourpi01 systemd[257521]: snapd.session-agent.socket: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Closed REST API socket for snapd user session agent. Jun 25 11:26:32 fourpi01 systemd[257521]: Reached target Shutdown. Jun 25 11:26:32 fourpi01 systemd[257521]: systemd-exit.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[257521]: Finished Exit the Session. Jun 25 11:26:32 fourpi01 systemd[257521]: Reached target Exit the Session. Jun 25 11:26:32 fourpi01 systemd[1]: systemd-logind.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped Login Service. Jun 25 11:26:32 fourpi01 systemd[1]: user at 1002.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped User Manager for UID 1002. Jun 25 11:26:32 fourpi01 systemd[1]: unbound-resolvconf.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped Unbound DNS server via resolvconf. Jun 25 11:26:32 fourpi01 systemd[1]: Stopping Unbound DNS server... Jun 25 11:26:32 fourpi01 systemd[1]: Stopping User Runtime Directory /run/user/1002... Jun 25 11:26:32 fourpi01 systemd[1]: run-user-1002.mount: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Unmounted /run/user/1002. Jun 25 11:26:32 fourpi01 systemd[1]: user-runtime-dir at 1002.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped User Runtime Directory /run/user/1002. Jun 25 11:26:32 fourpi01 systemd[1]: Removed slice User Slice of UID 1002. Jun 25 11:26:32 fourpi01 systemd[1]: Stopping Permit User Sessions... Jun 25 11:26:32 fourpi01 systemd[1]: blk-availability.service: Succeeded. Jun 25 11:26:32 fourpi01 systemd[1]: Stopped Availability of block devices. Jun 25 11:26:32 fourpi01 systemd[1]: systemd-user-sessions.service: Succeeded. -- Reboot -- --snip-- # So the system does poweroff. RPi is using SSD # After this the UPS resets ... # Command used to perform reboot. --snip-- shutdown -r now reboot --snip-- # Following services are started by systemd at boot: --snip-- root at fourpi01:~# systemctl list-units | grep nut nut-driver.service loaded active running Network UPS Tools - power device driver controller nut-server.service loaded active running Network UPS Tools - power devices information server --snip-- Cheers, Yogi On Fri, Jun 26, 2020 at 3:58 PM Roger Price <roger at rogerprice.org> wrote:> > On Fri, 26 Jun 2020, Yogesh Bhanu wrote: > > > Hi Roger et.al, > > > > The shutdown /reset of UPS is near instantaneous after rpi reboots or > > switches off. > > FWIW -- It looks like something is off with Ubuntu 20.04 -- I tried > > with raspbian and arch linux using the same nut configuration on the > > same hardware and the UPS does not reset. > > Could you describe the exact procedure you use to reboot. The commands you use, > the systemd service unit involved, and the relevant entries in the system log. > > Roger > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Reasonably Related Threads
- reboot of nut managment node resets Tripplite SMX1000LCD
- reboot of nut managment node resets Tripplite SMX1000LCD
- reboot of nut managment node resets Tripplite SMX1000LCD
- reboot of nut managment node resets Tripplite SMX1000LCD
- NUT -2.7.4 with Tripp Lite SMX1000 LCD on RPI4 runing 64bit ubuntu 20.04