Pogoplug E02 Very Slow to Reboot (Shutdown)

[steadybright]

Since my initial request has gone unanswered, I'll ask a different question:

How can I view a log of what's happening with my Pogoplug E02 between when I issue the "reboot" command, and when I'm able to SSH into the Pogoplug following the reboot?

I've reviewed the logs that both journalctl and journalctl -b commands yield. Neither depicts any significant time gaps in the respective log entries, and the reboot took over an hour this morning.

I believe the problem is delayed shutdown, not a delayed start-up. I want to find out what's failing at shutdown and rectify the problem.

Thank you for any useful guidance you can provide.

steady

[moonman]

The best way is to setup netconsole or use serial.

[steadybright]

moonman, thank you for responding.

I'll give serial a shot (cable on order).

steady

[steadybright]

I was able to get the following log:

$this->bbcode_second_pass_quote('', '[') 35.476063] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 35.487735] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 3856.750986] systemd-update-utmp[697]: Failed to get D-Bus connection: Failed to authenticate in time.
[ 4366.640991] systemd[1]: systemd-update-utmp.service: control process exited, code=exited status=1
[ 4486.648648] systemd[1]: Unit systemd-update-utmp.service entered failed state.
[ 5746.664069] systemd[1]: Shutting down.
[ 5757.010623] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended
[ 5757.019193] EXT3-fs (sda1): using internal journal

[pepedog]

Is dbus starting?
viewtopic.php?f=31&t=6408&p=35903#p35911

[steadybright]

Yes, when I run systemctl command, among the lines listed is:

$this->bbcode_second_pass_quote('', 'd')bus.service loaded active running D-Bus System Message Bus

[steadybright]

To add to my previous post:

In addition to dbus.service, systemctl also shows dbus.socket loaded, active, and running.

[steadybright]

I disabled journal writing to disk by modifying the journald.conf file.

My system now reboots (shuts down) normally.

However, I don't consider my system fixed.

1. Is there a way to "re-install" journal with default settings? (I suppose my current journal install got corrupted), or
2. Is there something better than, or at least equivalent to, journal out there, such as syslog-ng, etc.?

Thank you to anyone knowledgeable enough and willing to help me with this.

steady

[moonman]

it may be flushing the log to the drive. There is an option to set storage to none or syslog-ng in jornald.conf

[steadybright]

Hi Moonman,

That is exactly how I "fixed" the problem.

What I'd like to do is get journal working again, as it used to.

I'm currently running syslog-ns, but with the limited resources of a Pogoplug V2, I'd to minimize the number of active processes. I can certainly live with syslog-ng, but I'd prefer to restore journal to working as it used to and remove syslog-ns for the sake of conserving available system resources. To do that, I need to find out how to restore journal to its virgin state.

Any ideas on how to do that?

Thanks,

steady