Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: unite07 on January 08, 2007, 04:24:35 AM
-
I did the update using the servermanager. After the reconfigure i noticed my vpn didnt work any longer.
when i go to the software installer in the servermanager it reads:
Please Wait - Yum Running (postreposetup)
the page reloads it's self every 30 seconds but it always reads the same.
In the shell i have run yum clean, and yum update it errors out saying that yum is allready running.
So...
If I reconfigure the server and run yum before opening the servermanager (which starts yum i assume)
i get this error:
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in ?
yummain.main(sys.argv[1:])
File "/usr/share/yum-cli/yummain.py", line 97, in main
result, resultmsgs = do()
File "/usr/share/yum-cli/cli.py", line 596, in doCommands
return self.search()
File "/usr/share/yum-cli/cli.py", line 1216, in search
matching = self.searchPackages(searchlist, args, callback=self.matchcallback)
File "__init__.py", line 1061, in searchPackages
File "/usr/share/yum-cli/cli.py", line 75, in doRepoSetup
self.doSackSetup(thisrepo=thisrepo)
File "__init__.py", line 260, in doSackSetup
File "repos.py", line 287, in populateSack
File "sqlitecache.py", line 96, in getPrimary
File "sqlitecache.py", line 83, in _getbase
File "sqlitecache.py", line 79, in getDatabase
File "sqlitecache.py", line 239, in makeSqliteCacheFile
File "sqlitecache.py", line 150, in createTablesPrimary
File "sqlitecache.py", line 188, in createDbInfo
File "/var/tmp/python-sqlite-root//usr/lib/python2.3/site-packages/sqlite/main.py", line 237, in execute
File "/var/tmp/python-sqlite-root//usr/lib/python2.3/site-packages/sqlite/main.py", line 515, in _begin
MemoryError
no mem for new parser
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.3/atexit.py", line 20, in _run_exitfuncs
func(*targs, **kargs)
File "plugins.py", line 152, in run
MemoryError
My biggest problem is the vpn not working.
everything else seems to work.
any suggestion is greatly appreciated
-
My biggest problem is the vpn not working.
everything else seems to work.
any suggestion is greatly appreciated
Start here. (http://forums.contribs.org/index.php?topic=35025.msg152598#msg152598)
-
Before i posted i read through the page you linked too. and it seamed the server was booting up using the smp kernel. I have since change that.
uname -r
2.6.9-42.0.3.EL
rpm -qa | grep kernel
kernel-smp-2.6.9-34.EL
kernel-utils-2.4-13.1.80
kernel-smp-2.6.9-34.0.2.EL
kernel-2.6.9-34.EL
kernel-2.6.9-34.0.2.EL
kernel-smp-2.6.9-42.0.2.EL
kernel-smp-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-smp-2.6.9-42.0.3.EL
kernel-2.6.9-42.0.3.EL
kernel-2.6.9-42.0.2.EL
kernel-smp-module-appletalk-1.0-1_2.6.9_42.0.2.EL
kernel-module-appletalk-1.0-1_2.6.9_42.0.2.EL
I still cant get the vpn to accept connections. And the update is still in limbo
-
i get this error:
All things which don't "just work" should be reported via the Bug Tracker.
-
Before i posted i read through the page you linked too. and it seamed the server was booting up using the smp kernel. I have since change that.
uname -r
2.6.9-42.0.3.EL
rpm -qa | grep kernel
kernel-smp-2.6.9-34.EL
kernel-utils-2.4-13.1.80
kernel-smp-2.6.9-34.0.2.EL
kernel-2.6.9-34.EL
kernel-2.6.9-34.0.2.EL
kernel-smp-2.6.9-42.0.2.EL
kernel-smp-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-smp-2.6.9-42.0.3.EL
kernel-2.6.9-42.0.3.EL
kernel-2.6.9-42.0.2.EL
kernel-smp-module-appletalk-1.0-1_2.6.9_42.0.2.EL
kernel-module-appletalk-1.0-1_2.6.9_42.0.2.EL
I still cant get the vpn to accept connections. And the update is still in limbo
The issue is not smp or up. It is the kernel modules matching your kernel.
It appears that in your case they don't. Change your booting kernel to 2.6.9_42.0.2.EL . Pick smp if you have multiple processors/cores/hyperthreading.
You are still at 7.0 going by what modules you have. 7.1 will give you something like..
[root@tiger ~]# rpm -qa | grep kmod
kmod-ppp-smp-1.0.2-1.2.6.9_42.0.3.EL
kmod-slip-1.0-1.2.6.9_42.0.3.EL
kmod-slip-smp-1.0-1.2.6.9_42.0.3.EL
kmod-ppp-1.0.2-1.2.6.9_42.0.3.EL
kmod-appletalk-smp-1.0-1.2.6.9_42.0.3.EL
kmod-appletalk-1.0-1.2.6.9_42.0.3.EL
[root@tiger ~]#
The above is a workaround but wont solve the underlying problem for the next person.
As per Charlie's advise, search through the Bugtracker for a similar bug and add to it or create a new one.
Post a link here to the bug for others to follow.
-
I can't believe i was so oblivious. Now the vpn works.
I will check out the bug tracker regarding the update problem.
Yum is still crapping out.
It seems as if i have half of the 7.1 update. the server-manager says 7.1 is installed but as you pointed out the modules are 7.0.
on to the bug tracker
thank you
-
I can't believe i was so oblivious. Now the vpn works.
I will check out the bug tracker regarding the update problem.
Yum is still crapping out.
It seems as if i have half of the 7.1 update. the server-manager says 7.1 is installed but as you pointed out the modules are 7.0.
on to the bug tracker
thank you
Hmm.. yum probably knows that you have the new kernels installed so it wont try again.
Try removing the kernels.. not sure how...
The following removes way too much
yum remove kernel-2.6.9-42.0.3.EL
yum remove kernel-smp-2.6.9-42.0.3.EL
Maybe
rpm -e --nodeps kernel-2.6.9-42.0.3.EL
rpm -e --nodeps kernel-smp-2.6.9-42.0.3.EL
Or just go to the Bug Tracker.
-
Seems like I ended up in a similar way. The server stopped working, or at least it didn't keep on updating. So made a shutdown but when I rebooted and went to update in server-manager it told me it had to reconfigure. But it was at package pop3 [x of huge number]. There appears to be a lot package lost. The reconfigure worked but now I seems to end up with a half 7.1 SME.
Maybee the both problems are related, maybee it's not. But I sure hope there is a good solution to make a full update to the server.
-
The solution is simple:
1.) go to bugtracker
2.) search for bug
3.) post a bug
4.) wait for solution