Why does upgrading webmin modules through virtualmin often fail?

7 posts / 0 new
Last post
#1 Sun, 03/25/2007 - 05:22
Dirk

Why does upgrading webmin modules through virtualmin often fail?

Hi, all the time or at least very often when upgrading webmin modules through the webinterface will fail. When I try to do an packages sync with upgrade again, it states I need to do a: dpkg --configure -a first.

Why is that? Anything I do wrong?

dsp

Sun, 06/07/2009 - 07:02
Dirk

Its still the case:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

Why does upgrade don't run smoothly when triggered via virtualmin webinterface?

Dirk

Sun, 06/07/2009 - 07:02
Dirk

Its still the case:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

Why does upgrade don't run smoothly when triggered via virtualmin webinterface?

Dirk

Sun, 06/07/2009 - 07:02
Joe
Joe's picture

Hey Dirk,

I'm not seeing this problem, though I am running into lots of dependency stupidity on my Debian development system (it's kinda messy since I didn't know much about Debian when I set it up).

Are there any other messages? I've never seen this particular error, and googling turns up nothing.

--

Check out the forum guidelines!

Sun, 06/07/2009 - 07:02
Dirk

Its still the case:
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

Why does upgrade don't run smoothly when triggered via virtualmin webinterface?

Dirk

Sun, 06/07/2009 - 07:02
Joe
Joe's picture

Hey Dirk,

I'm not seeing this problem, though I am running into lots of dependency stupidity on my Debian development system (it's kinda messy since I didn't know much about Debian when I set it up).

Are there any other messages? I've never seen this particular error, and googling turns up nothing.

--

Check out the forum guidelines!

Sun, 06/07/2009 - 07:02
Dirk

Hi Joe,
do you upgrade virtualmin through virtualmin webinterface itself? It just stops with the output at a certain point... Trying to redo causes the message mentioned.

I then enter the shell do the command and everything is fine.

Dirk

Topic locked