These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Postgres usage? on the new forum.
Web Hosting and Cloud Computing Control Panels
from my experience of playing around with webmin and virtualmin i have found that having postgre running or not running seems to make no difference to virtualmin and webmin, the postgre module that is built into webmin is for the instance that you decide to use postgre, if you do not have postgre installed it is safe to remove the module, also if you dont have any users using postgre then it is safe to remove entirely.
As Mike noted, Virtualmin and Webmin do not need PostgreSQL for anything.
There are several scripts that can use it, and it is a great database...but the majority of scripts are more comfortable, reliable, and better tested on MySQL, so it's probably wise to stick with it.
I will point out that you're probably not seeing attempted hacks...you're probably seeing the status checks that Webmin does when building the System Information page. PostgreSQL shouldn't be listening on any public ports, by default, and so it shouldn't be hackable from outside of your system (even if an exploit were discovered). If you're seeing a su to postgres every 10 minutes, it's just Webmin, and can be safely ignored.
But, no harm in disabling it if you don't need it and your users don't need it. In fact, it'll free up some memory.
--
Check out the forum guidelines!
Is there any way to disable these status checks if the postgres module is disabled?
In theory, the status checks wouldn't attempt to check Postgres if it's disabled.
Are you saying that although you disabled Postgres, you still get status notifications that it's down?
-Eric
Yes. Under Virtualmin -> System Settings -> Features and Plugins, PostgreSQL database is unchecked. This is where I disable it, right? Anyplace else i should look?
here is what I'm seeing in my logs:
Jul 5 18:35:03 kermit su: pam_unix(su:session): session opened for user postgres by (uid=0) Jul 5 18:35:03 kermit su: pam_unix(su:session): session closed for user postgres Jul 5 18:40:02 kermit su: pam_unix(su:session): session opened for user postgres by (uid=0) Jul 5 18:40:02 kermit su: pam_unix(su:session): session closed for user postgres Jul 5 18:45:02 kermit su: pam_unix(su:session): session opened for user postgres by (uid=0) Jul 5 18:45:02 kermit su: pam_unix(su:session): session closed for user postgres Jul 5 18:50:02 kermit su: pam_unix(su:session): session opened for user postgres by (uid=0) Jul 5 18:50:02 kermit su: pam_unix(su:session): session closed for user postgres Jul 5 18:55:03 kermit su: pam_unix(su:session): session opened for user postgres by (uid=0) Jul 5 18:55:03 kermit su: pam_unix(su:session): session closed for user postgres
Thanks for the information; I have disabled PostgreSQL, and for one week, no failures! And you are correct, that little bit of extra memory and the fact that it is one less service to hack is good.