libipkg.so.0 ipkg won't update

[Kram SSengor]

I have been using Alt-F for a few years now.    I am now using

DNS-323 Alt-F-0.1RC4.1-DNS-323-rev-A1B1C1.bin 

I believe it happened when I was compiling a unison ipk.  The unison ipk has worked well for quite some time.

However I lost the ability to upgrade my system.  

 ipkg update

ipkg-cl: can't load library 'libipkg.so.0'   in /usr/lib I have libipkg.so.0.0.0

I get the same error when using the gui

ipkg-cl: can't load library 'libipkg.so.0'

No ipkg instalation found, install ipkg in:  and I say sda2  where / is located and the result is 

Alt-F already exists, you shouldn't supply a mountpoint.
ipkg-cl: can't load library 'libipkg.so.0'
ipkg-cl: can't load library 'libipkg.so.0'
ipkg: can't umount aufs branch, stopping services and retrying...
ipkg: can't umount aufs branch, exiting.

Another error  - on the status page

awk: cmd. line:1: Unexpected end of string sh: °C/°F: bad number sh: °C/°F: bad number sh: °C/°F: bad number sh: bad number sh: bad number sh: bad number

Under the system page

The box is currently running Alt-F 0.1RC3 and its firmware is Alt-F-0.1RC4.1, kernel 3.10.32.

Thanks in advance.

[Joao Cardoso]

On Saturday, February 13, 2016 at 10:08:59 PM UTC, Kram SSengor wrote:

I have been using Alt-F for a few years now.    I am now using

DNS-323 Alt-F-0.1RC4.1-DNS-323-rev-A1B1C1.bin 

I believe it happened when I was compiling a unison ipk.

In the box?

 

 The unison ipk has worked well for quite some time.

And you didn't share it with us :-( ? 

That means that you also have ocaml. Did you compiled it also yourself? Do you mind sharing?

However I lost the ability to upgrade my system.  

 ipkg update

ipkg-cl: can't load library 'libipkg.so.0'   in /usr/lib I have libipkg.so.0.0.0

Both libipkg.so and libipkg.so.0 are links to the real library, ibipkg.so.0.0.0

You must have

[root@dns-323a]# ls -l /usr/lib/libipkg.so*

lrwxrwxrwx    1 root     root            16 Feb 10 17:26 /usr/lib/libipkg.so -> libipkg.so.0.0.0

lrwxrwxrwx    1 root     root            16 Feb 10 17:26 /usr/lib/libipkg.so.0 -> libipkg.so.0.0.0

-rwxr-xr-x    1 root     root        147544 Jun 24  2014 /usr/lib/libipkg.so.0.0.0 

Run

ldconfig /usr/lib/

to reestablish the links

I get the same error when using the gui

ipkg-cl: can't load library 'libipkg.so.0'

No ipkg instalation found, install ipkg in:  and I say sda2  where / is located and the result is 

Alt-F already exists, you shouldn't supply a mountpoint.
ipkg-cl: can't load library 'libipkg.so.0'
ipkg-cl: can't load library 'libipkg.so.0'
ipkg: can't umount aufs branch, stopping services and retrying...
ipkg: can't umount aufs branch, exiting.

Another error  - on the status page

awk: cmd. line:1: Unexpected end of string sh: °C/°F: bad number sh: °C/°F: bad number sh: °C/°F: bad number sh: bad number sh: bad number sh: bad number

That is unrelated and already fixed in one of the last releases.

 

Under the system page

The box is currently running Alt-F 0.1RC3 and its firmware is Alt-F-0.1RC4.1, kernel 3.10.32.

Running RC3 with RC4.1 flashed? For any special reason?

 

Thanks in advance.

[Kram SSengor]

On Saturday, February 13, 2016 at 4:08:59 PM UTC-6, Kram SSengor wrote:

I have been using Alt-F for a few years now.    I am now using

I get the same error when using the gui

ipkg-cl: can't load library 'libipkg.so.0'

No ipkg instalation found, install ipkg in:  and I say sda2  where / is located and the result is    :EDIT FIXED

Another error  - on the status page

awk: cmd. line:1: Unexpected end of string sh: °C/°F: bad number sh: °C/°F: bad number sh: °C/°F: bad number sh: bad number sh: bad number sh: bad number  : EDIT Returns after reboot

NEW

Before I got the reply I changed the name o flibipkg.so.0.0.0 to  libipkg.so.0 - ipkg worked. I did use your advice, renamed back to previous, and did the "ldconfig /usr/lib/" It worked and locate also works now, I had complaints of a bad ncurses library also that does not appear.  

For a seperate post I will try to get you ocaml and unison.  Actually I do not have a .ipk, just the binary.  I did compile it via compiling ocaml 3.12.1 and then to unison 2.40.102  I will have to try to find the original webpages I used.  I  believe that one I used was http://www.daymz.com/2014-05-09_building-unison-for-dns-323-nas/

Another thing I did long ago was to make a static /root to hold /root/.unison  .  I do not know if that caused problems, I was using info from the funplug forum

Progress thanks.  

Stilll a problem is using command line "poweroff" or the gui poweroff only reboots.  

Still, I can flash and receive "Everything looks OK. The firmware file is for a DNS-323 and you have a rev-DNS-323-B1 board." and then proceed via TryIt and the FlashIt and the awk complaints disappear - but when I reboot, it goes back to the RC3 RC4.1 hybrid.  I can live with that, it is weird.   

But for me, it is all about backup, and my unison works as does my root permanently on /mnt/sda2

[Joao Cardoso]

On Wednesday, February 17, 2016 at 1:06:32 AM UTC, Kram SSengor wrote:

On Saturday, February 13, 2016 at 4:08:59 PM UTC-6, Kram SSengor wrote:

I have been using Alt-F for a few years now.    I am now using

I get the same error when using the gui

ipkg-cl: can't load library 'libipkg.so.0'

No ipkg instalation found, install ipkg in:  and I say sda2  where / is located and the result is    :EDIT FIXED

Another error  - on the status page

awk: cmd. line:1: Unexpected end of string sh: °C/°F: bad number sh: °C/°F: bad number sh: °C/°F: bad number sh: bad number sh: bad number sh: bad number  : EDIT Returns after reboot

NEW

Before I got the reply I changed the name o flibipkg.so.0.0.0 to  libipkg.so.0 - ipkg worked. I did use your advice, renamed back to previous, and did the "ldconfig /usr/lib/" It worked and locate also works now, I had complaints of a bad ncurses library also that does not appear.  

For a seperate post I will try to get you ocaml and unison.  Actually I do not have a .ipk, just the binary.  I did compile it via compiling ocaml 3.12.1 and then to unison 2.40.102  I will have to try to find the original webpages I used.  I  believe that one I used was http://www.daymz.com/2014-05-09_building-unison-for-dns-323-nas/

Another thing I did long ago was to make a static /root to hold /root/.unison  .  I do not know if that caused problems, I was using info from the funplug forum

That can cause issues with flashing/TryIt.

Use instead a userboot script to run at boot and do your own initialization, such as copying ssh key, or other: Services->System->User, e.g.:

[root@DNS-323a]# cat /mnt/sda2/startup.sh 

#!/bin/sh

exec >> /var/log/user.log 2>&1

case "$1" in

         start) 

waitfor="md0 sda2" # customize for your needs    

for i in $waitfor; do

    echo -n "waiting for $i:"

    while ! mountpoint -q /mnt/$i; do

        echo -n '.'

        sleep 5

    done

    echo OK

done

echo -n "Waiting for aufs.sh to finish:" 

while ! aufs.sh -s >& /dev/null; do

        echo -n '.'

        sleep 1

done

echo OK

cp -a /mnt/sda2/.ssh /root

        ;;

        stop) ;;

        *) ;;

esac

You might have difficulties getting rid of /Alt-F/root

Progress thanks.  

Stilll a problem is using command line "poweroff" or the gui poweroff only reboots.  

Still, I can flash and receive "Everything looks OK. The firmware file is for a DNS-323 and you have a rev-DNS-323-B1 board." and then proceed via TryIt and the FlashIt and the awk complaints disappear - but when I reboot, it goes back to the RC3 RC4.1 hybrid.  I can live with that, it is weird.   

Probably the /Alt-F/root existence can explain all the above.

In any case you have some leftovers from RC3/4 under /Alt-F. The easiest way to get rid of them is using 'fixup clean', or System->Utilities->Fixes, Remove All.

Use the 'fixup' first. Still with the 'awk' errors? RC4.1 shown in the Status page? No? Flashing error, get rid of /Alt-F/root (you must do that anyway, reboot needed, 'aufs.sh needed)

[Kram SSengor]

On Saturday, February 13, 2016 at 4:08:59 PM UTC-6, Kram SSengor wrote:

I have been using Alt-F for a few years now.    I am now using

DNS-323 Alt-F-0.1RC4.1-DNS-323-rev-A1B1C1.bin 

...

 On the command line "fixup clean" took a few seconds and finished. Is "fixup clean" something like dpkg --configure -a?  And I got much more beautiful page stating that I had RC4.1 in firmware and as os.  I had no flashing errors,  "reboot" worked.  "poweroff" works now also.  And a after the scheduled checkup of sda2 - unison works as well as locate and mc. I did not have to delete /Alt-F/root in the firmware.  I am not sure what to do with the script.  

I will retry compiling ocaml, etc. and getting real .ipks out if possible - seperate post.  I will mark as solved after a day.  

[João Cardoso]

On Thursday, 18 February 2016 02:22:59 UTC, Kram SSengor wrote:

On Saturday, February 13, 2016 at 4:08:59 PM UTC-6, Kram SSengor wrote:

I have been using Alt-F for a few years now.    I am now using

DNS-323 Alt-F-0.1RC4.1-DNS-323-rev-A1B1C1.bin 

...

 On the command line "fixup clean" took a few seconds and finished. Is "fixup clean" something like dpkg --configure -a?

No, it just removes any files under /Alt-F that are modifications from the base firmware and are not configuration settings, nor disk-installable files.

 

 And I got much more beautiful page stating that I had RC4.1 in firmware and as os.  I had no flashing errors,  "reboot" worked.  "poweroff" works now also.  And a after the scheduled checkup of sda2 - unison works as well as locate and mc.

Good

 

I did not have to delete /Alt-F/root in the firmware.

Since RC4.1 the existence of /Alt-F/root is of no concern, so you can keep it and have no issues.

 I am not sure what to do with the script.  

If you don't know what to do with it, do nothing :-)

Its explained in the wiki: https://sourceforge.net/p/alt-f/wiki/Customize%20Firmware/

 

I will retry compiling ocaml, etc. and getting real .ipks out if possible - seperate post.  I will mark as solved after a day.  

I don't need/want binaries, but the  "receipt" to cross-compile them. Specially ocaml. I remember that I once was able to cross-compile it but could not automate the build procedure.