pwAdmin not accessible suddenly
My actual server started having issues yesterday then appeared to go offline. When I tried to access pwAdmin to see what was going on I could not access it. Did a stop.sh, restarted entire machine then start.sh, however still no access to pwAdmin. I'm not getting any errors when starting back up. Thinking it may be an apache issue, but not sure. I am using 343's release and had been running just fine until now. Any thoughts or suggestion for what could be causing pwAdmin to not be accessible and how hard it would be to re install apache would be appreciated. Thanks in advance.
Re: pwAdmin not accessible suddenly
Do you do the whole ./jetty start and ./jetty stop?
I have this problem, but I don't use 343's release so I dunno.
Type ./jetty stop wait 3 seconds and then type ./jetty start.
That always helped me, in extreme cases I did a full machine reboot and then did the ./jetty stop and ./jetty start commands.
Good luck, I hate when pwadmin goes all buggy :<
Re: pwAdmin not accessible suddenly
Quote:
Originally Posted by
M a g i c
Do you do the whole ./jetty start and ./jetty stop?
I have this problem, but I don't use 343's release so I dunno.
Type ./jetty stop wait 3 seconds and then type ./jetty start.
That always helped me, in extreme cases I did a full machine reboot and then did the ./jetty stop and ./jetty start commands.
Good luck, I hate when pwadmin goes all buggy :<
i do that daily with cron because it tends to use more and more ram over time :D
The only difference is that i use a properly installed jetty which is called with /etc/init.d/jetty restart.
Re: pwAdmin not accessible suddenly
Never used anything with jetty, typed ./jetty stop from root and I got
-bash: ./jetty: No such file or directory
Re: pwAdmin not accessible suddenly
Quote:
Originally Posted by
crxfreak
Never used anything with jetty, typed ./jetty stop from root and I got
-bash: ./jetty: No such file or directory
if my suggestion does not work, i guess you need to navigate to the jetty folder then before typing ./jetty, as it is not supposed to be in your root folder unless you linked it there.
Re: pwAdmin not accessible suddenly
he does not have jetty installed, he is using apache 5.5.28 i am actually researching on how to install jetty right now
Re: pwAdmin not accessible suddenly
pwAdmin comes bundled with jetty and has done for a long time. Are you using some ancient release of pwAdmin?
Installation instructions here...
pwTools
If you are using tomcat have you tried stopping an starting tomcat again?
I think it was as follows.
Code:
./tomcat_stop.sh
./tomcat_start.sh
Also maybe try clearing the Tomcat cache of pwAdmin.
If all else fails just reinstall pwAdmin.
Re: pwAdmin not accessible suddenly
ok im attepting to reinatll pwadmin. and looks like the steps i have taken are the same in the write up you linked. however i am having dificulty locating the start up script. is it the start.jar?
Re: pwAdmin not accessible suddenly
Nope its the file called "jetty" with no extension.
Just run
and it will start the "jetty" service
Re: pwAdmin not accessible suddenly
ok according to the screen jetty is starting but i had to have missed somthing, cause pwadmin isnt showing up, i did have to edit the jetty file from php-cgi to php (there is not a php-cgi file"link" in the /usr/bin/ directory however there is a php directory)
PowerEdge-SC1420:~# ./jetty start
-bash: ./jetty: No such file or directory
PowerEdge-SC1420:~# sudo /etc/init.d/jetty start
php-cgi started
jetty started
PowerEdge-SC1420:~#
Re: pwAdmin not accessible suddenly
OK reinstalled apache and it should be running as I can access the Registration Page, however pwAdmin still doesn't come up. Any other suggestions?
Re: pwAdmin not accessible suddenly
Quote:
Originally Posted by
crxfreak
OK reinstalled apache and it should be running as I can access the Registration Page, however pwAdmin still doesn't come up. Any other suggestions?
You're using my release correct?
Attempt to delete the ../work/ in tomcat...
(rm -R /opt/apache-tomcat-5.5.28/2/work)
I have never had the problem you seem to be describing, but any time I have had any small 'hang-ups' deleting 'work' always seemed to do the trick :wink:
If that doesn't work you would want to attempt a re-installation of tomcat (not the HTTP apache)... You could even 're-install' the one from my ISO:
rm -R /opt/apache-tomcat-5.5.28
(then mount the ISO)
cp -R /cdrom-mountpoint/opt/apache-tomcat-5.5.28 /opt/
Hope this helps :):
Re: pwAdmin not accessible suddenly
OK re installing tomcat from the iso got pwAdmin to come back up. Thank you very much!!