ipkg upgrade output

[Tellus1]

For the last couple of days, after issuing "ipkg upgrade" command, I always get the following output:

Configuring cyrus-sasl

Please read the man page of saslauthd and
check settings in /opt/etc/init.d/S52saslauthd

If you dislike the link /usr/lib/sasl2 -> /opt/lib/sasl2
then you may want to set SASL_PATH instead

(re)starting service saslauthd
postinst script returned status 1
ERROR: cyrus-sasl.postinst returned 1
Nothing to be done
Successfully terminated.

What is the reason for this and what should I do?

[wpte]

since every time you want to install cyrus-sasl during upgrade and fails it stays in the list to be upgraded.
perhaps the easiest way is by removing cyrus-sasl and reinstalling it

ipkg remove cyrus-sasl
ipkg update
ipkg install cyrus-sasl

now hopefully ipkg upgrade should work fine

[Tellus1]

Still the same error. I'll try a few more tricks in this direction.

[avberk]

If you do an 'ipkg install' on an existing package it should do an upgrade automatically.

otherwise you could probably delete this file:

/opt/lib/ipkg/lists/optware

and then do ipkg update

Hope that helps..

[Tellus1]

I moved/renamed the file /opt/lib/ipkg/lists/optware and repeated ipkg update and ipkg upgrade - this time the output was without the "extra" lines. Thanks.

Although I'm not 100% the optware file had anything to do with it (esp. because the old file and the new file had the same size). Maybe it had to do with this file:
/opt/var/state/saslauthd/saslauthd.pid

...especially since the following lines were always in the log when starting the reboot:

<35>saslauthd[2797]: detach_tty: could not lock pid file /opt/var/state/saslauthd/saslauthd.pid: resource temporarily unavailable
<35>saslauthd[2796]: detach_tty: cannot start saslauthd
<35>saslauthd[2796]: detach_tty: another instance of saslauthd is currently running

Namely, in the same session as deleting the optware file, I also killed this process:

150 ?        Ss     0:00 /opt/sbin/saslauthd -a getpwent -n 1

which was then automatically restarted. Maybe this solved the issue. As for the reason "why" this all happened, the mystery still remains.