Came across this in a support request
The following errors were found :
- The SVN config directory does not exist.
- The SVN password file does not exist.
- The SVN access file does not exist.
The solution is before installing svnmanager run:
svnadmin create ~/repos
As the user you want to install it as.
Then rerun the installer. Make sure the repo path is /path/to/user/repos
This was an odd one. I found a few servers which had their /tmp permissions changed to user clamav with permissions 711.
Turned out clamav home was set to /tmp causing this during an upcp. A which script to check / fix
tmpcheck='cat /etc/passwd | grep ^clamav: | cut -d: -f6';
echo "Warning /tmp set as homedir for user clamav";
if [ "$tmpcheck" = "/tmp" ]; then
if [ ! -e /usr/local/clamav ]; then
mkdir -p /usr/local/clamav
chown clamav:clamav /usr/local/clamav
usermod -d /usr/local/clamav clamav
echo '/usr/local/clamav already exists, no changes made';
This will create clamav home as /usr/local/clamav, only if it does not exist already. Another option may be /home/clamav
InterServer’s customer portal at https://my.interserver.net provides a lot addons included in the price. Many of these are for VPS’s (kvm/openvz) or InterServer quickservers. Here is a small list of features:
1) Backup creation – under system management under the VPS you can create a backup of a running VPS. For KVM there is no downtime, and with openvz there is a small amount of downtime for backups. These are stored on interserver cloud storage systems and does not count toward your space usage. These backups can be restored onto a new VPS or a reinstall with the same VPS.
2) Server monitoring – under the monitoring tab in my.interserver.net you can monitor an external IP address for services like ping or httpd. Email can be sent on failure.
3) DNS Control – using cdns1/cdns2/cdns3.interserver.net under my.interserver.net -> domains -> dns manager create and manage your own dns records. These dns servers are geo distributed (NJ and LA). Great for a small vps looking to lower memory usage by not running a separate dns server.
4) Reboot / stop / start and reinstall under system management.
5) Out of band VNC – KVM only – set up vnc to connect out of band to your system. You can connect even if networking is down on your VPS. A similar feature coming soon for openvz.
6) Tons of OS choices available now – Gentoo / Centos / Debian / Ubuntu / Windows 2008/2012 and more.
7) Purchase additional harddrive space – under system management. You don’t need to add additional slices to increase just disk space on your VPS.
8) Add additional slices – under system management. Increase cpu / memory / disk space and bandwidth limit all at once.
All of the above can be done with out contacting support for assistance.
On occasion an RPM db can get corrupt on RHEL based systems. Running rpm -vv –rebuilddb after backing up /var/lib/rpm is a quick fix to the problem.
I came across the following error during a yum update, on an openvz container
(process:7450): GLib-CRITICAL **: g_timer_stop: assertion `timer != NULL' failed
(process:7450): GLib-CRITICAL **: g_timer_destroy: assertion `timer !=
TypeError: Can not create db_info table: database is locked
Now my immediate thought was rpm db, but that was not the case. This was from a sqlite file in /var/cache/yum.
Cleaning the headers / all in yum did not help, in this case I had to restart the openvz container to release the lock on the database.