install totaly messed up

[bbunlock]

I have just moved to a new server and transfered all my files over etc and also installed wine using yum, however I had a script on my site that used wine (via exec command) that no longer worked after the transfer to the new server.

I tried a few things on the server thinking it was a problem with current setup but got nowhere, I then uninstalled wine via "yum erase wine" and reinstalled but still no luck getting the script to work, I then addred the &> out.txt to the end of the command line argument for wine to log any error and it had the following line of text "wine: cannot open /root/.wine : Permission denied".

I loged in to the server via ssh and tried the command via ssh and it worked fine but it would not work via the script, but I was loged in as root I loged out and loged in as the user for the website and when I ran the very same command and I got the following error.

preloader: Warning: failed to reserve range 00110000-60000000
Segmentation fault (core dumped)

This same script worked perfectly well on the old server but its just not having it on this server.

the script is obviously trying to run as root from the website becuase of the "/root/.wine" part of the error I mentioned above when I imagine it should be running as the account user becuase the account user also has a .wine folder in my home folder "/home/mysite/.wine"

can anyone offer any advice on getting this to run as the normal user without the reserve range error

regards

wayne

[austin987]

On Wed, Jul 8, 2009 at 5:47 PM, bbunlock<[email protected]> wrote:

I have just moved to a new server and transfered all my files over etc and also installed wine using yum, however I had a script on my site that used wine (via exec command) that no longer worked after the transfer to the new server.

I tried a few things on the server thinking it was a problem with current setup but got nowhere, I then uninstalled wine via "yum erase wine" and reinstalled but still no luck getting the script to work, I then addred the &> out.txt to the end of the command line argument for wine to log any error and it had the following line of text "wine: cannot open /root/.wine : Permission denied".

I loged in to the server via ssh and tried the command via ssh and it worked fine but it would not work via the script, but I was loged in as root I loged out and loged in as the user for the website and when I ran the very same command and I got the following error.

preloader: Warning: failed to reserve range 00110000-60000000
Segmentation fault (core dumped)

This same script worked perfectly well on the old server but its just not having it on this server.

the script is obviously trying to run as root from the website becuase of the "/root/.wine" part of the error I mentioned above when I imagine it should be running as the account user becuase the account user also has a .wine folder in my home folder "/home/mysite/.wine"

can anyone offer any advice on getting this to run as the normal user without the reserve range error

regards

wayne

http://wiki.winehq.org/PreloaderPageZeroProblem

--
-Austin

[bbunlock]

Thanks for the reply Austin but I have already tried that fix and I still just get "preloader: Warning: failed to reserve range 00110000-60000000
Segmentation fault (core dumped)" when I run it as the account owner, still works fine as root though?

any other ideas would be appriciated

regards

wayne

[bbunlock]

I still havnt managed to get this working, I have uninstalled wine with yum but wine files are still on the system because even after removing with yum I can still run wine from root?

how can wine still be on my system if I have removed it with yum?

Does anyone know how to remove wine from my system? I was thinking that after it has been removed I could try that later release 1.1.25 as im currently using 1.0.1 which was installed via yum

I cant understand why this is screwed up on my system but no matter what I do it will only work if run by root user, normal user keeps giving me the same "preloader: Warning: failed to reserve range 00110000-60000000" and I have tried the fix for this and still getting this error

any help appriciated

regards

wayne

[austin987]

On Thu, Jul 9, 2009 at 2:16 PM, bbunlock<[email protected]> wrote:

I still havnt managed to get this working, I have uninstalled wine with yum but wine files are still on the system because even after removing with yum I can still run wine from root?

how can wine still be on my system if I have removed it with yum?

What does `which -a wine` show?


--
-Austin

[bbunlock]

Hi Austin

the command you gave shows the following "/usr/bin/wine"

regards

wayne

[austin987]

On Thu, Jul 9, 2009 at 3:38 PM, bbunlock<[email protected]> wrote:

Hi Austin

the command you gave shows the following "/usr/bin/wine"

You somehow installed it there then...Did you build from source and
use 'make install'? You'll need to 'make uninstall' first.


--
-Austin

[bbunlock]

Hi Austin

I have never built from source when installing wine, I have only ever used rpm's to install wine and for the most part I have only used yum to install it, I will give you a very brief history of my experience with wine on this server (worked fine on last server)

new server setup so everything was done by loging in as root to begin with so I may have first installed wine as root but I think that is ok as long as I dont use it as root.

so first install possibly while loged in as root
web script that worked on old server no longer worked

when I uninstalled wine the first time I was loged in as super user and not direct root login so I loged in as normal user then su - to log in as supper user (which is root if im not mistaken)

tried script again and still not working, now the install and uninstall went on for a couple of more times but never isntalled via cource, now no matter if its installed or removed via yum there is always a wine working on my system? yum may not say there is but there is.

tried the code for the script while loged in as normal web owner and get the out or range message, tried exact same line while loged in as su - and line works perfect.

have noticed that in the error message left from the web script that it mentions the following "wine: cannot open /root/.wine : Permission denied" which means the wine is being used as root in my web script and not account holder? on old server it ran wine as normal web account owner as I do have a .wine in my home dir.

any suggestions?

regards

wayne

[bbunlock]

I have done some more digging on the net and it seems that the error I get about reserve range is not the same thing as the bug listed on here, it turns out it looks like a fix is available if you set "ulimit -v unlimited" but the user does not have the rights to do this, can be done from root but that only sets it for root.

I have edited the /etc/profile to set all -v to unlimited, restarted httpd, loged out of ssh, rebooted the server and when I log in as the user it still says 200000 and not unlimited, dont suppose anyone knows how I can change it to unlimited

regards

wayne

[walt]

On 07/09/2009 02:02 PM, bbunlock wrote:

...
have noticed that in the error message left from the web script that
it mentions the following "wine: cannot open /root/.wine : Permission
denied" which means the wine is being used as root in my web script
and not account holder?...

Well, if wine is running as root it should be able to open /root/.wine
I would think. Someone please correct me if I'm wrong.

Maybe wine is running as 'web' or 'apache' or some similar name in your
/etc/group file? What are the permissions on wine and your web script?

[walt]

On 07/09/2009 05:21 PM, bbunlock wrote:

I have done some more digging on the net and it seems that the error I get
about reserve range is not the same thing as the bug listed on here, it
turns out it looks like a fix is available if you set "ulimit -v unlimited"
but the user does not have the rights to do this...

I don't know what your script is doing, but you might try adding that ulimit
command at the beginning of the script? Might be worth a try, anyway.