install problem

7 posts / 0 new
Last post
#1 Wed, 06/18/2008 - 17:37
florin.burada

install problem

Postinstall setup .. Out of memory!

Will the computer just run away with my memory at this time? Or shall I wait it out, and the install script will finally finish? I've noticed ALL RAM is now used after that run-postinstall.pl script is ran, and HD constantly swaps as of now...

shall I just wait it out overnight, and let it to continue to swap? or is this a memory leak?

this is a 3.02gz machine with 1gig DDR ram installed....

what's causing the issue with the postinstall stuff?

usermin installs fine!

help!

I have a feeling this is either because of the newer debian OS, or because I had a previous install of webmin.

find / -name webmin can't find anything though. Is there some config files I've missed or something?

Webmin/Usermin were both uninstalled using the uninstall.sh scripts!!

Wed, 06/18/2008 - 17:42
cesurasean

Ok, I was able to get webmin started, WHILE the .deb package is still stuck at: Setting up Webmin.....

Is it ok if I just edit the source and remove the postinstall script? What exactly is it's purpose?

Webmin seems to be fine without it being ran yet...

if you want access to my server, let me know...

thanks

Wed, 06/18/2008 - 17:52 (Reply to #2)
cesurasean

Running postinstall scripts ..
Out of memory!

This is the EXACT error message when I install from source, and what also seems to make the .deb package get stuck....

run-postinstall just RUNS away with all of my memory for some reason.

I've bypassed the postinstall for now. Hopefully someone can tell me HOW important that script actually is, or what it accomplishes.

Thank you!

Wed, 06/18/2008 - 18:35 (Reply to #3)
andreychek

Howdy,

You certainly made quick work of this problem ;-) (not working to installed in 20 minutes!)

Now, as for that memory error -- since you've uninstalled Webmin, it looks like the postinstall essentially does two things:

1. Setup an init script and start webmin

2. Run the following setup script (which is a 850 line script that says it's setting up config files and such): ./setup.sh >/tmp/.webmin/webmin-setup.out

Now, that command is interesting as it means there might be some debugging info available.

Do you see any interesting information in "/tmp/.webmin/webmin-setup.out"?

Also, can you verify that there aren't any stray versions of webmin running? (ps aux|grep miniserv|grep webmin)

Thanks,
-Eric

Wed, 06/18/2008 - 17:55 (Reply to #4)
cesurasean

Ok, now installing Virtualmin just gets stuck.

Seems that miniserv.pl just RUNS off with my memory, the same as run-postinstall does.

Can someone help me fix this, or do I need to reformat and build my server? :( - I would hate this as a solution. :(

Wed, 06/18/2008 - 18:49
cesurasean

I haven't looked into that file /tmp/.webmin/webmin-setup.out yet.....

because im going to TRY and rsync all my files BACK to my machine, and see if everything gets restored like it should. <crosses fingers> ( never restored from rsync backups as of yet. this is 1st time try )

There was NO other webmin's installed. I even ran a find to look for webmin files...

How come miniserv.pl was RUNNING away with memory, just like run-whateveritscalled.pl does? I was unable to reinstall virtualmin once I had gotten webmin running from /etc/init.d/webmin start ...

I think this is a bug somewhere that needs to be addressed, but I don't have time to save my system resources to prove this point. Sorry.

Thu, 06/19/2008 - 14:04 (Reply to #6)
Joe
Joe's picture

<div class='quote'>How come miniserv.pl was RUNNING away with memory, just like run-whateveritscalled.pl does?</div>

It doesn't. At least not for any of the rest of us. ;-)

We need to figure out what is happening on your system that makes it run away with all the memory--1GB should be more than enough for installation.

<div class='quote'>I think this is a bug somewhere that needs to be addressed, but I don't have time to save my system resources to prove this point. Sorry.</div>

If we can't reproduce it, we can't fix it. No one else has reported similar problems...so, there's nothing we can do about it. Sorry.

--

Check out the forum guidelines!

Topic locked