Can't ssh to Pogo again

This forum is for all other ARMv5 devices

Re: Can't ssh to Pogo again

Postby chat1410 » Tue Jan 22, 2013 2:07 am

I upgraded today and also received the message regarding nss-myhostname and systemd. In addition, I received the following messages during the upgrade:

$this->bbcode_second_pass_code('', '
2013-01-21 17:20] ==> Warning: setcap failed, falling back to setuid root on /usr/bin/systemd-detect-virt
[2013-01-21 17:20] ==> Persistent net naming rules have been shipped as disabled.
[2013-01-21 17:20] See /etc/udev/rules.d/80-net-name-slot.rules for more detail
')
Post upgrade, I rebooted my PogoPlug and it came right back up.

Unfortunately OXNAS is well behind the rest of the Arch user base. Arch has retired init and transitioned to systemd while the older OXNAS kernel doesn't support systemd. This has and will continue to cause issues as individual packages drop their support for init.
chat1410
 
Posts: 28
Joined: Thu Nov 01, 2012 5:55 pm

Re: Can't ssh to Pogo again

Postby dinjo » Tue Jan 22, 2013 10:26 am

Yes i also got the same warning can developers comment
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am

Re: Can't ssh to Pogo again

Postby pepedog » Tue Jan 22, 2013 10:38 am

That message also appears on other devices, like here
viewtopic.php?f=18&t=4760
Happens when one thing is taken away, but expected to be there, and replaced by something else
Are you working again, like chat1410 OXNAS is?
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Can't ssh to Pogo again

Postby dinjo » Thu Jan 24, 2013 1:57 am

Ever since I reinstall nss my hostname it seems working
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am

Re: Can't ssh to Pogo again

Postby dinjo » Sat Feb 23, 2013 9:18 am

Seems its back and see what i have here non working pogo

$this->bbcode_second_pass_code('', 'looking for inter-conflicts...

Targets (9): binutils-2.23.1-3 ffmpeg-1:1.1.2-3 gcc-4.7.2-4 gcc-libs-4.7.2-4 glibc-2.17-3 php-5.4.12-1 php-apache-5.4.12-1 php-cgi-5.4.12-1 php-fpm-5.4.12-1

Total Installed Size: 162.14 MiB
Net Upgrade Size: 0.12 MiB

Proceed with installation? [Y/n] y
(9/9) checking package integrity [#######################################################################################] 100%
(9/9) loading package files [#######################################################################################] 100%
(9/9) checking for file conflicts [#######################################################################################] 100%
(9/9) checking available disk space [#######################################################################################] 100%
(1/9) upgrading glibc [#######################################################################################] 100%
call to execv failed (No such file or directory)
error: command failed to execute correctly
(2/9) upgrading binutils [#######################################################################################] 100%
call to execv failed (No such file or directory)
error: command failed to execute correctly
(3/9) upgrading ffmpeg [#######################################################################################] 100%
(4/9) upgrading gcc-libs [#######################################################################################] 100%
(5/9) upgrading gcc [#######################################################################################] 100%
call to execv failed (No such file or directory)
error: command failed to execute correctly
(6/9) upgrading php [#######################################################################################] 100%
(7/9) upgrading php-apache [#######################################################################################] 100%
(8/9) upgrading php-cgi [#######################################################################################] 100%
(9/9) upgrading php-fpm [#######################################################################################] 100%
call to execv failed (No such file or directory)
error: command failed to execute correctly
[root@alarm ~]$ ls
-bash: /usr/bin/ls: No such file or directory
')
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am

Re: Can't ssh to Pogo again

Postby dinjo » Mon Feb 25, 2013 4:57 am

I was able to fix it by running below command

$this->bbcode_second_pass_code('', '/usr/lib/ld-2.17.so /usr/bin/pacman -S filesystem')
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am

Re: Can't ssh to Pogo again

Postby hojnikb » Fri Mar 08, 2013 9:21 pm

I've just broke my freshly setup dockstar. Used the latest rootfs, booted into it and ofcourse ran pacman. And guess what, it broke my filesystem.

Is there a solution for or shuld i just avoid updating for a while ?
(i think this also broke my old installation, becouse i couldn't log in wth ssh, which made me to make a fresh install)
+°´°+,¸¸,+°´°~ +°´°+,¸¸,+°´°~I ♥ my DockStar :oops:~°´°+,¸¸,+°´°++°´°+,¸¸,+°´°~
Linux = Be root
Windows = reboot

+°´°+,¸¸,+°´°~DockStar, Marvell CPU @ 1.2Ghz, 128MB RAM, 4GB rootfs + 160GB°´°+,¸¸,+°´°+
hojnikb
 
Posts: 104
Joined: Thu Jul 08, 2010 11:57 am

Re: Can't ssh to Pogo again

Postby dinjo » Mon Mar 11, 2013 7:33 am

What all packages are getting updated ?
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am

Re: Can't ssh to Pogo again

Postby dinjo » Sat Mar 23, 2013 3:59 am

Again filesystem error while upgrading

$this->bbcode_second_pass_code('', 'looking for inter-conflicts...

Targets (1): filesystem-2013.03-2

Total Installed Size: 0.31 MiB
Net Upgrade Size: 0.00 MiB

Proceed with installation? [Y/n] y
(1/1) checking package integrity [#######################################################################################] 100%
(1/1) loading package files [#######################################################################################] 100%
(1/1) checking for file conflicts [#######################################################################################] 100%
(1/1) checking available disk space [#######################################################################################] 100%
(1/1) upgrading filesystem [#######################################################################################] 100%
warning: directory permissions differ on srv/http/
filesystem: 777 package: 755
warning: directory permissions differ on sys/
filesystem: 755 package: 555
error: extract: not overwriting dir with file var/run
error: problem occurred while upgrading filesystem
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.
')
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am

Re: Can't ssh to Pogo again

Postby Geoff » Sat Mar 23, 2013 10:09 pm

Geoff
 
Posts: 231
Joined: Wed Mar 09, 2011 5:14 pm

PreviousNext

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 13 guests