Litespeed Web Server constantly restarts when updating MaxMind's (GeoIP) databases

[savvos]

Hello!

I run a cron job that automatically gets the mmdb files from an external server I own.

However, when the download completes (almost always within seconds), Litespeed Web Server restarts indefinitely and every website becomes inaccessible. I need to kill the processes and restart Litespeed for it to work properly.

Any ideas?

 

[serpent_driver]

Documentation is your friend.

https://docs.litespeedtech.com/lsws/cp/cpanel/geoip/#geoip-rewrite-rules-infinite-loop

 

[savvos]

I think that you copied the wrong part, but I found out from a Reddit post that the right hierarchy of actions is:
Remove existing database > Copy new ones > Restart Web Server.

Is that right? How will the websites not crash between the time of removal and the copy? Am I missing something?

 

[serpent_driver]

Is that right?

LiteSpeed support should answer this question.

 

[savvos]

Is this forum even operational? @serpent_driver does a better job than the Staff themselves at this point...
Two weeks and no response for a paid product is crazy.

 

[serpent_driver]

Is this forum even operational? @serpent_driver does a better job than the Staff themselves at this point...
Two weeks and no response for a paid product is crazy.

If you have paid license you should contact LiteSpeed support directly. e.g. support@litespeedtech.com

 

[savvos]

You're right; however, the same issue may occur for another user, which is why I prefer the forum. We need to address these issues publicly to save the support's valuable time.

 

[serpent_driver]

You're right; however, the same issue may occur for another user, which is why I prefer the forum. We need to address these issues publicly to save the support's valuable time.

Try this: https://golitespeed.slack.com/

 

[Unique_Eric]

Hi @savvos
I set up a fresh LSWS instance using the GeoLite2-Country.mmdb database and confirmed that a test site is correctly using GeoIP. I ran continuous requests to the site using curl while attempting different database update methods:

1. Directly uploading the new file into the GeoIP directory
2. Downloading a new database file and moving it into place with the production filename
3. Removing the existing database, copying in the new one, and restarting the web server

In all cases, I was unable to reproduce the issue. If you're still able to reproduce it, please open a support ticket with us so we can help further.