no attempt to autoupdate...

[jrmarino]

Hi -
I've got 3.0.1 installed on a Solaris 10 system. I had to put the configuration aside for a couple of weeks to deal with other things. Since I've come back, I've realized that 2 minor versions have been released since.

My litespeed install has been running the entire time, yet there has been no attempt to even check if there is another version available. The only two lines in the autoupdate/update.log are:

[2007-04-12 18:27:52] Checking for new release...
[2007-04-12 18:27:52] [OK] Package is uptodate.

I tried to run the update agent from the command line, and it scolded me not too!

I've restarted it server twice to see if a restart would check for an update. It's set for DAILY checks.

Any idea what's wrong?

[mistwang]

Maybe something wrong with the solaris update agant. We will check.

[jrmarino]

I have some additional information.

I'm in the process of installing version 3.1 on another server. I've noticed that it is check for updates each time I restart the server. The autoupdate log supports this as well as the error log.

Perhaps between 3.01 and 3.10 this problem was corrected along the way.

If so, how do I upgrade manually?
Can I get wget the file and run an upgrade script -- is that equivalent?

[mistwang]

Just run install.sh and select "upgrade", same result as doing it from web admin. Maybe the awstats problem was fixed as well.

[jrmarino]

Ok, I successfully upgraded the server.

However, the first server is still not even attempting to check for updates. The awstats problem was also not fixed.

The first and second servers are identical in every way. Same make, model, operating system, and configuration. Kind of a mystery...

[jrmarino]

I think I'm getting somewhere!

THe second server had the "auto restart = yes" which is wrong. I turned it off and now it no longer checks for updates.

Is it possible that auto restart and the update parameter are linked together? If so, should they be? It does not seem like it should be.

[jrmarino]

That's definitely the problem.

As soon as I turned autorestart = yes on the first server, it checks for an update and created the awstats configuration (awstats works now).

Can you please explain why this autostart parameters affects these seemingly unrelated things?

[mistwang]

"Auto restart" should be "Yes" for most setup, it helps restoring the service immediately if one lshttpd crashes. To me, there is no down side of doing this.

[mistwang]

update checking and awstats update are done in the watchdog process, if "auto start" is set to "no", those steps probably is skipped.

Maybe we should remove this option from our web console, and let it on all the time.

[jrmarino]

Solaris 10 does this natively with the SMF functionality, and I want Solaris to handle it. There's your downside, and that's a legitimate reason.

However, that statement still doesn't explain why "auto restart = no" breaks awstats and the auto update.