2,411
edits
Changes
From SME Server
Jump to navigationJump to searchUpdating from SME 7.1.x or earlier (view source)
Revision as of 09:02, 15 October 2007
, 09:02, 15 October 2007Removed the kill command as it is of nou use to kill processes that are doing valuable work, just have some patience instead.
This probably indicates that your yum repositories are misconfigured. You should follow the standard [[#Yum_Update]] procedure above.
This probably indicates that your yum repositories are misconfigured. You should follow the standard [[#Yum_Update]] procedure above.
====Existing lock /var/run/yum.pid: another copy is running. Aborting.====
====Existing lock /var/run/yum.pid: another copy is running. Aborting.====
SME runs yum automatically to check for available updates. If this background check is running you will see this error. You can either wait for the background process to finish, or abort it using:
SME runs yum automatically to check for available updates. If this background check is running you will see this error. Just wait a few minutes for the background process to finish.
====GLib-CRITICAL **: file gtimer.c: line 106 (g_timer_stop)====
====GLib-CRITICAL **: file gtimer.c: line 106 (g_timer_stop)====
This error indicates that you have installed yum packages that require later versions of sqlite and python-sqlite than you have installed on your system. You can recover using the commands shown below. Note that the specific versions listed for python-sqlite and sqlite may change!
This error indicates that you have installed yum packages that require later versions of sqlite and python-sqlite than you have installed on your system. You can recover using the commands shown below. Note that the specific versions listed for python-sqlite and sqlite may change!
