GoFlex Home boot time problems

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

GoFlex Home boot time problems

Postby VicTic » Tue Nov 19, 2013 3:53 am

I hope I'm submitting this to correct subforum.

I'm running Arch on Goflex Home 3TB.

When I reboot my system, the transmission service is running but not accessible via web UI. When I investigated the problem, I also noticed timestamp during boot is wrong.

$this->bbcode_second_pass_code('', '[root@alarm ~]# uname -a
Linux alarm 3.1.10-28-ARCH #1 PREEMPT Thu Oct 17 22:11:45 CDT 2013 armv5tel GNU/Linux
[root@alarm ~]# systemctl status transmission
transmission.service - Transmission BitTorrent Daemon
Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
Active: active (running) since Fri 2015-02-20 22:23:02 EST
Main PID: 233 (transmission-da)
Status: "Idle."
CGroup: /system.slice/transmission.service
└─233 /usr/bin/transmission-daemon -f --log-error

Feb 20 22:23:02 alarm systemd[1]: Started Transmission BitTorrent Daemon.
Feb 20 22:23:02 alarm transmission-daemon[233]: sendto: Network is unreachable')

Please note the timestamp and "running since".

Restarting service corrects the problem:
$this->bbcode_second_pass_code('', '[root@alarm ~]# systemctl restart transmission
[root@alarm ~]# systemctl status transmission
transmission.service - Transmission BitTorrent Daemon
Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
Active: active (running) since Sun 2013-11-17 13:19:40 EST; 2s ago
Main PID: 395 (transmission-da)
Status: "Idle."
CGroup: /system.slice/transmission.service
└─395 /usr/bin/transmission-daemon -f --log-error

Nov 17 13:19:40 alarm systemd[1]: Starting Transmission BitTorrent Daemon...
Nov 17 13:19:40 alarm systemd[1]: Started Transmission BitTorrent Daemon.')

The service file:

$this->bbcode_second_pass_code('', '[root@alarm ~]# cat /usr/lib/systemd/system/transmission.service
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target

[Service]
User=transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error

[Install]
WantedBy=multi-user.target')

So, two questions:

* What's with the wrong time during boot? If I do "systemctl status ..." for any service, it shows that the service is running since Feb 20 2015, 22:23, no matter when was the last reboot. The hardware clock was synchronized (hwclock --systohc) and "hwclock -r" shows correct time.

* How do I get rid of "sendto: Network is unreachable" in transmission service on boot?

Thank you!
VicTic
 
Posts: 5
Joined: Tue Nov 19, 2013 3:36 am

Re: GoFlex Home boot time problems

Postby tomcheng76 » Tue Nov 19, 2013 7:04 am

Try to add the following to [Service] entry in file /etc/systemd/system/transmission.service


$this->bbcode_second_pass_code('', 'Type=forking
PIDFile=/run/transmission/transmission.pid')
tomcheng76
 
Posts: 130
Joined: Mon Dec 13, 2010 11:24 am

Re: GoFlex Home boot time problems

Postby VicTic » Tue Nov 19, 2013 2:30 pm

I tried that. You said "add" but there was already "Type=notify" so I replaced that line with "Type=forking" - was I right?

Results:
1) The same error during boot.
2) The command "systemctl start/restart transmission" never returns, although it does start transmission and makes web GUI available.

$this->bbcode_second_pass_code('', '[root@alarm ~]# systemctl status transmission
transmission.service
Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
Active: activating (start) since Fri 2015-02-20 22:23:15 EST
Control: 227 (transmission-da)
CGroup: /system.slice/transmission.service
└─227 /usr/bin/transmission-daemon -f --log-error

Feb 20 22:23:16 alarm transmission-daemon[227]: sendto: Network is unreachable
[root@alarm ~]# systemctl restart transmission
^C
[root@alarm ~]# systemctl status transmission
transmission.service
Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
Active: activating (start) since Tue 2013-11-19 09:16:47 EST; 54s ago
Control: 389 (transmission-da)
CGroup: /system.slice/transmission.service
└─389 /usr/bin/transmission-daemon -f --log-error

Nov 19 09:16:47 alarm systemd[1]: Starting transmission.service...')
VicTic
 
Posts: 5
Joined: Tue Nov 19, 2013 3:36 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 41 guests