| View previous topic :: View next topic |
| Author |
Message |
milothurston
Apprentice
Joined: 01 May 2002
Posts: 231
Location: Oxford, England.
|
 Posted: Mon Sep 09, 2002 1:28 pm Post subject: Portsentry not starting |
 |
|
I've been seeing this when trying to start portsentry:
| Code: |
bioinf1 portsentry # /etc/init.d/portsentry start
* Starting portsentry...
ERROR: Configuration files are missing/corrupted.
ERROR: Check your syslog for a more detailed error message.
ERROR: PortSentry is shutting down!
ERROR: Configuration files are missing/corrupted.
ERROR: Check your syslog for a more detailed error message.
ERROR: PortSentry is shutting down!
|
However, the files are the default ones installed with the package, renamed and edited. I also tried with files I know to be working (copied from Red Hat and Debian machines here), and they give the same result.
There are no entries in syslog to explain this.
Is there some peculiarity of the gentoo portsentry package that I should know about?
Thanks,
Milo. |
|
| Back to top |
|
 |
RebelYell
n00b
Joined: 28 Jun 2002
Posts: 41
|
| Posted: Tue Sep 10, 2002 1:17 pm Post subject: Re: Portsentry not starting |
|
|
| milothurston wrote: | I've been seeing this when trying to start portsentry:
| Code: |
bioinf1 portsentry # /etc/init.d/portsentry start
* Starting portsentry...
ERROR: Configuration files are missing/corrupted.
ERROR: Check your syslog for a more detailed error message.
ERROR: PortSentry is shutting down!
ERROR: Configuration files are missing/corrupted.
ERROR: Check your syslog for a more detailed error message.
ERROR: PortSentry is shutting down!
|
However, the files are the default ones installed with the package, renamed and edited. I also tried with files I know to be working (copied from Red Hat and Debian machines here), and they give the same result.
There are no entries in syslog to explain this.
Is there some peculiarity of the gentoo portsentry package that I should know about?
Thanks,
Milo. |
For some reason i've got the same error... (looks like the ebuild is not modifying the .h file which contains the hard-coded portsentry's config file path - the line with sed). If you're gonna take a look in the logs, you'll see that portsentry's looking for config files in /usr/local/psionic blah-blah.
Your config files are located in /etc/portsentry, right?
A quick fix could be:
Take the source from /usr/portage/distfiles/portsentry*
Unpack-it somewhere on your disk
Manually edit the .h file containing the hard-coded paths. (i don't rememer the filename right now, but it is in readme install file)
Do a make linux (but not make install).
Copy the resulted portsentry binary where your actual portsentry resides.
Now it should work.
Good luck!
Over and Out,
Rebel Yell |
|
| Back to top |
|
|
milothurston
Apprentice
Joined: 01 May 2002
Posts: 231
Location: Oxford, England.
|
| Posted: Tue Sep 10, 2002 1:29 pm Post subject: |
|
|
That did the trick, thanks. 
The file was portsentry_config.h.
Milo. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
