| View previous topic :: View next topic |
| Author |
Message |
crs992
-
Joined: 15 Jun 2005
Posts: 32
|
 Posted: Tue Mar 07, 2006 11:03 pm Post subject: cannot listen to console port |
 |
|
whenever i restart my computer when everything is loading abyss always says "cannot listen to console port" so i change the console port from 9999 ro 10000 and then restart. it then says there is a listening problem on port 8080 which is the port my server is on. i then have to open "cports"-a program that allows me to see what programs are running and which port they are running on. i then close port 9999 and restart again and it finaly works. does anyone know how i can change something so when i restart it abyss will load properly? please help if you can. thanks.
-chuck
_________________
http://crs992.bounceme.net:8080/ |
|
| Back to top |
   |
 |
AbyssUnderground
-
Joined: 31 Dec 2004
Posts: 3855
|
| Posted: Wed Mar 08, 2006 12:08 am Post subject: |
|
|
You might be trying to run abyss as a service AND load it up as a normal program. This will cause the conflict you describe.
_________________
Andy (AbyssUnderground) (previously The Inquisitor)
www.abyssunderground.co.uk |
|
| Back to top |
|
|
crs992
-
Joined: 15 Jun 2005
Posts: 32
|
|
| Back to top |
|
|
fpuhan
-
Joined: 04 Apr 2006
Posts: 1
|
| Posted: Tue Apr 04, 2006 2:42 pm Post subject: |
|
|
| The Inquisitor wrote: | | You might be trying to run abyss as a service AND load it up as a normal program. This will cause the conflict you describe. |
I read this with interest because I think I've encountered the same situation:
I have Mac OS X 10.4.6 (just patched this morning). Upon restart (my first since installing and configuring Abyss WS X1) I found I could not access the console through port 9999.
When I ran Abyss as an application, it came up nicely and put its icon in the dock. When it started as a service, no icon appeared, although it was serving web pages nicely. However, I could not then access the console.
When I check Activity Monitor, I saw two abyssws processes running. One was process id 179, owned by root, and the other was process id 180, owned by my account. I do not have Abyss set as a login item on my account preferences.
I killed both processes and started the application. It came up normally, and I reset it to not be a startup item.
It's now running normally, but I'm curious if this is expected behavior (to not be able to access the console when running as a system startup item) or not. Could the update to OS X 10.4.6 somehow have closed a security hole? |
|
| Back to top |
|
|
AbyssUnderground
-
Joined: 31 Dec 2004
Posts: 3855
|
| Posted: Tue Apr 04, 2006 4:32 pm Post subject: |
|
|
It is normal not to see an icon during a service startup but you can still access the console on the console port. It may not be 9999 depending on how you set up abyss.
For example my console port is 10000 not 9999.
_________________
Andy (AbyssUnderground) (previously The Inquisitor)
www.abyssunderground.co.uk |
|
| Back to top |
|
|
aprelium
-
Joined: 22 Mar 2002
Posts: 6800
|
| Posted: Tue Apr 04, 2006 7:59 pm Post subject: |
|
|
fpuhan,
When Abyss Web Server is launched as a service (or a Startup Item as it is called on Mac OS X), it runs in the background and does not show any icon on the dock. That's how services or Startup items are supposed to work: in the background with no interaction with the session of the user currently logged in.
But you can still access your console by opening your browser and entering http://127.0.0.1:9999 (9999 is the default console port but it could be another value if you have changed it) in the address bar.
_________________
Support Team
Aprelium - http://www.aprelium.com |
|
| Back to top |
 |
|
|
