PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001506PacketFenceconfigurationpublic2012-08-07 17:532012-10-22 13:04
ReporterOndaje 
Assigned Tofdurand 
PrioritynormalSeveritytrivialReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version3.5.0 
Target Version3.6.0Fixed in Version3.6.0 
fixed in git revision5083b422602f08e103dcb152db1d5f845525a5f5
fixed in mtn revision
Summary0001506: Packetfence's configurator port should be configurable (and changed from 3000 to 1444)
DescriptionAfter installing PacketFence onto a debian box that already had Ntop installed, I am unable to access the PacketFence web configurator, hence unable to use PacketFence.

Ntop uses port 3000 just like Catalyst's development server default port.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-08-07 17:53OndajeNew Issue
2012-08-07 18:24fdurandNote Added: 0002914
2012-08-07 18:55OndajeNote Added: 0002915
2012-08-08 08:50obilodeauStatusnew => assigned
2012-08-08 08:50obilodeauAssigned To => fdurand
2012-08-08 08:51obilodeauNote Added: 0002917
2012-08-08 08:51obilodeauSeverityminor => trivial
2012-08-08 08:51obilodeauTarget Version => +1
2012-08-08 08:51obilodeauSummaryPacketfence's configurator does not start if NTOP is installed. => Packetfence's configurator port should be configurable (and changed from 3000 to 1444)
2012-08-08 08:51obilodeauDescription Updated
2012-08-08 09:22fdurandNote Added: 0002920
2012-08-08 11:30OndajeNote Added: 0002922
2012-10-19 13:50fgaudreaultTarget Versiongeneral => 3.6.0
2012-10-19 13:50fgaudreaultNote Added: 0003177
2012-10-22 13:04fgaudreaultgit revision => 5083b422602f08e103dcb152db1d5f845525a5f5
2012-10-22 13:04fgaudreaultNote Added: 0003218
2012-10-22 13:04fgaudreaultStatusassigned => resolved
2012-10-22 13:04fgaudreaultResolutionopen => fixed
2012-10-22 13:04fgaudreaultFixed in Version => 3.6.0

Notes
(0002914)
fdurand   
2012-08-07 18:24   
To change the default port 3000 to 3001, in the pfappserver init script change _start function like that:

_start() {
  iptables -I INPUT -p tcp --dport 3001 -j ACCEPT
  start-stop-daemon --start --port 3001 --quiet --pidfile $PIDFILE -m --chdir $APPDIR \
    ${USER:+"--chuid"} $USER ${GROUP:+"--group"} $GROUP --background \
    --startas $APPDIR/script/${UNIXNAME}_server.pl
(0002915)
Ondaje   
2012-08-07 18:55   
Hmm. When i run service pfappserver restart, it fails to start. Any way to view the error?
(0002917)
obilodeau   
2012-08-08 08:51   
Updated title, description and triaged.
(0002920)
fdurand   
2012-08-08 09:22   
Sorry for the mistake

_start() {
  iptables -I INPUT -p tcp --dport 3001 -j ACCEPT
  start-stop-daemon --start --quiet --pidfile $PIDFILE -m --chdir $APPDIR \
    ${USER:+"--chuid"} $USER ${GROUP:+"--group"} $GROUP --background \
    --startas $APPDIR/script/${UNIXNAME}_server.pl -- -p 3001
(0002922)
Ondaje   
2012-08-08 11:30   
That fixed it! Thanks!
(0003177)
fgaudreault   
2012-10-19 13:50   
Target for 3.6.0.
(0003218)
fgaudreault   
2012-10-22 13:04   
Fixed in commit 5083b422602f08e103dcb152db1d5f845525a5f5