New update release 4.2.2-ent is available, please download.

Discussion in 'Install/Configuration' started by bobykus, Mar 8, 2013.

  1. bobykus

    bobykus Member

    Got this last morning. I'm already on 4.2.2-ent, so what happens? What is updated? Any changelog to see?
  2. Yogesh Sarkar

    Yogesh Sarkar Banned

    I believe they just updated their auto update servers, nothing has changed for those of us, who had manually updated.
  3. Michael

    Michael Administrator

    Actually, even though the version numbers don't change, we're putting out new builds all the time in response to feedback and bug reports. We move a version to auto update when we're sure that, not only will some people benefit, but everyone should definitely use it.

    If you do a force reinstall in the WebAdmin interface now, you'll get a slightly more updated 4.2.2 than the one you currently have. (Heck, we put out a new build just this morning...)
  4. bobykus

    bobykus Member

    It is brilliant! How about changelog?
  5. Michael

    Michael Administrator

    Not yet. Sorry. It's on the to-do list.

    Most of the new builds address very, very, very specific problems anyway.

    It's definitely not a bad idea to force reinstall when you get the automated email, though: /lsws/admin/misc/lsup.sh -f or in the WebAdmin interface.
  6. Yogesh Sarkar

    Yogesh Sarkar Banned

    In that case, please release such builds as 4.2.2.x, otherwise people like me who upgrade initially, end up with the older builds.
  7. bobykus

    bobykus Member

    It's definitely not a bad idea to do a changelog first too :)
    I need to know what I apply, thought. Many depends on it.
  8. Michael

    Michael Administrator

    These are good points and we're working on the changelog. As far as adding a new number for every build, we do a lot of builds. I mean a lot, a lot... Almost all of them don't seem to warrant telling anyone except the person whose specific problem we were fixing... When they do seem like something that might affect a good number of people, we put out a new build number.

    But, as I said, y'all raise good points. I know you guys don't like getting kept in the dark. We're working on keeping the communications lines more open. Thanks for the feedback. We'll try to get on it.
  9. gellenburg

    gellenburg New Member

    [solved] *BUMP* Having the same issue.

    Bumping this thread back up. I'm having the exact same issue.

    Last week, LiteSpeed kept alerting me to upgrade (but I was already on 4.2.2-ent).

    So I just did a force reinstall within the WebAdmin interface just now, which went smoothly, and lsws gracefully restarted on its own.

    And I'm still getting the emails every few minutes.

    Since I'm coming in late to this party, let me just reiterate that in a production setting, and for proper change management, how important it is to have an accurate record of which software versions get installed when, and where.

    In addition, I would think LiteSpeedTech would want to know to aid in troubleshooting.

    I get that LS build lots (n
    Last edited by a moderator: Jun 12, 2013
  10. Michael

    Michael Administrator

    Hello Gellenburg,

    Sorry to take so long to get back to you. We think you getting these emails may be a combination of two issues:

    1. The directory /usr/local/lsws/autoupdate contains information on when the emails have been sent. We're wondering if the server doesn't have permission to write to the files in this directory and thus keep a record of what emails you've been sent.

    2. We think your server may be restarting frequently. This would be a symptom of an unrelated problem, but, if the directory above doesn't have a record that you'd already received an update notice today, then it will send out an update notice at restart. Have you been seeing many restarts?

    Sorry again for the delayed response.

    Michael
  11. gellenburg

    gellenburg New Member

    Here's the directory perms for /usr/local/lsws:

    Code:
    root@ussatdl01 [/usr/local/lsws]# ls -alrt
    total 92
    drwxr-xr-x   2 root  root  4096 Mar 31 05:12 lib/
    drwxr-xr-x  12 root  root  4096 Mar 31 05:12 add-ons/
    drwxr-xr-x   2 root  root  4096 Mar 31 05:12 php/
    drwxr-xr-x   7 root  root  4096 Mar 31 05:12 DEFAULT/
    drwxr-xr-x   2 root  root  4096 Mar 31 05:12 docs/
    drwxr-xr-x   2 root  root  4096 Mar 31 06:30 logs/
    drwx------   3 lsadm lsadm 4096 May 27 21:01 phpbuild/
    drwxr-xr-x  16 root  root  4096 May 27 21:06 ./
    drwxr-xr-x   7 root  root  4096 May 27 21:06 lsphp5/
    drwxr-xr-x   2 root  root  4096 May 28 06:41 fcgi-bin/
    drwxr-xr-x   2 root  root  4096 Jun  4 07:31 share/
    drwxr-xr-x   9 root  root  4096 Jun  4 07:31 admin/
    drwxr-xr-x   2 root  root  4096 Jun  4 07:31 bin/
    -rw-r--r--   1 root  root     6 Jun  4 07:31 VERSION
    -rw-r--r--   1 root  root  6959 Jun  4 07:31 LICENSE
    -rw-r--r--   1 root  root  2214 Jun  4 07:31 LICENSE.OpenLDAP
    -rw-r--r--   1 root  root  6279 Jun  4 07:31 LICENSE.OpenSSL
    -rw-r--r--   1 root  root  3208 Jun  4 07:31 LICENSE.PHP
    drwx------   2 lsadm lsadm 4096 Jun  4 07:31 autoupdate/
    drwxr-xr-x. 25 root  root  4096 Jun 11 01:02 ../
    drwx------   4 lsadm lsadm 4096 Jun 11 05:15 conf/
    root@ussatdl01 [/usr/local/lsws]# 
    
    And here's the contents of the autoupdate folder:

    Code:
    root@ussatdl01 [/usr/local/lsws]# cd autoupdate/
    root@ussatdl01 [/usr/local/lsws/autoupdate]# ls -alrt
    total 20
    -rw-r--r--  1 nobody nobody    9 Mar 31 12:59 release
    -rw-r--r--  1 nobody nobody   12 Mar 31 12:59 platform
    drwxr-xr-x 16 root   root   4096 May 27 21:06 ../
    -rw-r--r--  1 nobody nobody 1899 Jun  4 07:31 update.log
    drwx------  2 lsadm  lsadm  4096 Jun  4 07:31 ./
    -rw-r--r--  1 nobody nobody    0 Jun 11 15:13 .last
    root@ussatdl01 [/usr/local/lsws/autoupdate]# 
    
    (I'm still getting the emails.)

    How can I find this out?

    Thanks!
  12. Michael

    Michael Administrator

    Look for a file called lsrestart.log in lsws/logs.

    I'll be back about the permissions in a second.

    m
  13. gellenburg

    gellenburg New Member

    Here's the last 50 lines in the restart log:

    Code:
    root@ussatdl01 [/usr/local/lsws/logs]# tail -50 lsrestart.log 
    Mon Jun 10 04:53:57 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 05:02:25 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 07:15:55 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 08:14:44 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 09:14:24 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 11:11:13 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 13:08:03 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 15:04:53 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 17:01:43 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 19:15:13 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 21:12:03 EDT 2013
    restart, LSWS running: 1
    Mon Jun 10 23:08:53 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 01:05:45 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 01:06:58 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 01:07:14 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 01:07:41 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 03:12:49 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 05:01:40 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 05:10:07 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 07:06:58 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 08:05:47 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 09:06:07 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 11:02:57 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 13:16:27 EDT 2013
    restart, LSWS running: 1
    Tue Jun 11 15:13:18 EDT 2013
    restart, LSWS running: 1
    root@ussatdl01 [/usr/local/lsws/logs]# 
    
    
    I wonder why it's restarting so much? Had no idea it was doing this.
  14. Michael

    Michael Administrator

    Yes. Why it is restarting is the big question. There could be a number of reasons for this. (Too many 503 errors maybe? A bad application?) To the error logs, Batman!

    (You are, though, now seeing the beauty of LiteSpeed's graceful restart feature: You don't notice when it restarts.)

    As for the permissions, the permission for the release file are wrong. That's why it hasn't been updated since March and why your system doesn't know what version you have. I don't know how that happened, but deleting everything in the autoupdate directory should allow your server to repopulate the directory with the right files and stop the emails. (Backup first, of course!)

    m
  15. gellenburg

    gellenburg New Member

    Ok, done. I'm assuming that as soon as I restart the server it will auto-update?

    Code:
    root@ussatdl01 [/usr/local/lsws]# tar jcvf autoupdate-backup.tar.bz2 autoupdate/
    autoupdate/
    autoupdate/update.log
    autoupdate/platform
    autoupdate/release
    autoupdate/.last
    root@ussatdl01 [/usr/local/lsws]# cd autoupdate
    root@ussatdl01 [/usr/local/lsws/autoupdate]# rm -rf *
    root@ussatdl01 [/usr/local/lsws/autoupdate]# ls -alrt
    total 8
    -rw-r--r--  1 nobody nobody    0 Jun 11 15:13 .last
    drwxr-xr-x 16 root   root   4096 Jun 11 16:55 ../
    drwx------  2 lsadm  lsadm  4096 Jun 11 16:55 ./
    root@ussatdl01 [/usr/local/lsws/autoupdate]# rm .last
    rm: remove regular empty file `.last'? y
    root@ussatdl01 [/usr/local/lsws/autoupdate]# ls -alrt
    total 8
    drwxr-xr-x 16 root  root  4096 Jun 11 16:55 ../
    drwx------  2 lsadm lsadm 4096 Jun 11 16:55 ./
    root@ussatdl01 [/usr/local/lsws/autoupdate]# 
    
  16. gellenburg

    gellenburg New Member

    Code:
    root@ussatdl01 [/usr/local/lsws/autoupdate]# /etc/init.d/lsws restart
    root@ussatdl01 [/usr/local/lsws/autoupdate]# ls -alrt
    total 20
    drwxr-xr-x 16 root  root   4096 Jun 11 16:55 ../
    -rw-r--r--  1 root  nobody    0 Jun 11 16:57 .last
    -rw-r--r--  1 lsadm lsadm    12 Jun 11 16:57 platform
    drwx------  2 lsadm lsadm  4096 Jun 11 16:57 ./
    -rw-r--r--  1 lsadm lsadm   113 Jun 11 16:57 update.log
    -rw-r--r--  1 lsadm lsadm     9 Jun 11 16:57 release
    root@ussatdl01 [/usr/local/lsws/autoupdate]# 
    
  17. gellenburg

    gellenburg New Member

    Ok, that seems to have done the trick.

    Code:
    root@ussatdl01 [/usr/local/lsws/autoupdate]# cat update.log 
    [2013-06-11 16:57:06] Checking for new release...
    [2013-06-11 16:57:06] [OK] New release 4.2.3-ent is available.
    [2013-06-11 16:59:16] Extracting package file
    [2013-06-11 16:59:16] Upgrade to 4.2.3 successfully.
    [2013-06-11 16:59:18] Checking for new release...
    [2013-06-11 16:59:18] [OK] Package is up-to-date.
    root@ussatdl01 [/usr/local/lsws/autoupdate]# 
    
    Not really sure what all was going on, but I really appreciate your help in helping me get this sorted out!

    Thanks again.
  18. Michael

    Michael Administrator

    No problem. Would have loved to have gotten to this sooner, but other things kept intervening...

Share This Page