SELinux causing the lack of connectivity? On 9/16/2014 4:13 PM, Jay Tarbox wrote: > Netstat shows it's listening > > [root@asspnew ~]# netstat -l > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 10.1.1.97:smtp 0.0.0.0:* LISTEN > tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:54617 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:55553 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:55555 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:22222 0.0.0.0:* LISTEN > > -----Original Message----- > From: Jay Tarbox [mailto:jtar...@necomm.com] > Sent: September 16, 2014 15:57 > To: For Users of ASSP > Subject: Re: [Assp-user] Upgrade from 1.x to 2.x > > And now, I've got nothing on the new server. > I can't get to a web interface on port 55555 despite the below in the log: > > Sep-16-14 15:54:56 [init] Listening for SMTP connections on 10.1.1.97:25 > Sep-16-14 15:54:56 [init] Listening for admin HTTP connections on > 0.0.0.0:55555 0.0.0.0:22222 > Sep-16-14 15:54:56 [init] Listening for stat HTTP connections on 0.0.0.0:55553 > > > Sometimes I hate Linux so much. > > -----Original Message----- > From: Jay Tarbox [mailto:jtar...@necomm.com] > Sent: September 16, 2014 14:02 > To: For Users of ASSP > Subject: Re: [Assp-user] Upgrade from 1.x to 2.x > > For some reason I thought that ASSP 2 required a DB server. This is not the > case, eh? > I'm in a company with ~45 employees and processing ~2500 emails/day. > > -----Original Message----- > From: Grayhat [mailto:gray...@gmx.net] > Sent: September 16, 2014 09:14 > To: assp-user@lists.sourceforge.net > Subject: Re: [Assp-user] Upgrade from 1.x to 2.x > > :: On Mon, 15 Sep 2014 13:55:40 -0400 (EDT) > :: > <sig.2335687692.264015110.783.1410803740460.javamail.zim...@drdos.info> :: > Doug Lytle <supp...@drdos.info> wrote: > >>>> Should I upgrade inplace or load up a new server (virtual)? >> If you'd like a quick way to revert, then I'd roll a new VM. > agreed; setup a new, clean VM, install the needed prerequisites then proceed > setting up Perl and then ASSP, check if all the needed stuff is ok and > loaded, next, done that and using your v1 config, proceed configuring your v2 > to match your v1, if needed copy whatever config file (domains, regexp...) to > your v2 and ensure the v2 will load it; once done, copy your > spam/notspam/errors folders from v1 to v2 and run a rebuild, at that point > you should be ready to switch VMs and try using your v2 ... and if it doesn't > work, rolling back will be easy > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Assp-user mailing list > Assp-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-user > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Assp-user mailing list > Assp-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-user > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Assp-user mailing list > Assp-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-user > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Assp-user mailing list > Assp-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-user
------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
