[ic] Interchange server is unavailable

Mike Heins mike at perusion.com
Mon May 29 17:42:30 EDT 2006


Quoting sb at airdelights.com (sb at airdelights.com):
> "Music" <music at labyrinth.net.au> wrote:
> > >I performed a new installation of Interchange on Centos with apache  
> > >server and new installation of perl. Ran Interchange makecat and set 
> > >up  catalog with mysql.  Everything seems to go fine. On restart of  
> > >Interchange I get this message:  [root at localhost ~]# interchange 
> > >restart  Low traffic settings.
> > > Calling UI......UI is loaded...
> > > Interchange V5.5.0-200605230658
> > > Running with new signals, external programs could be unreliable.
> > > Re-run with environment variable PERL_SIGNALS set to "unsafe" to
> change
> > > this.
> > > Configuring catalog store...Using MySQL,
> > > DSN=dbi:mysql:test_store...done.
> > > The Interchange server is already running (process id 10151)
> > > 
> > > But when I go to the web page I get this message:
> > > We're sorry, the Interchange server is unavailable...
> > > We are out of service or may be experiencing high system demand. 
> > > Please try again soon.
> > 
> > Edit this file: /path/to/interchange/bin/interchange
> > and make the second line read:
> > $ENV{PERL_SIGNALS} = "unsafe";
> >
> >No - don't do that;  Put PERL_SIGNALS=unsafe in your environment before
> you start Interchange, or start/restart using the >following:
> >
> >    su ic_username -c "PERL_SIGNALS=unsafe /path/to/bin/interchange
> --restart"
> >
> >Although it's good to set PERL_SIGNALS, having it unset is unlikely to
> be the cause of the problem here.  The problem could be almost anything
> so check the error.log files for suspects.
> >
> >The problem may not even necessarily be in the Interchange core or
> installation.  The problem could be in the Apache setup >or with CGI
> permissions etc.  Check all of the log files for clues.
> 
> 
> Does this information help to pinpoint the problem?
> 
> May 29 14:14:28 localhost interchange: interchange shutdown succeeded
> May 29 14:14:28 localhost su(pam_unix)[11876]: session opened for user
> interch by sbronson(uid=0)
> May 29 14:14:28 localhost su[11876]: Warning!  Could not relabel
> /dev/pts/6 with user_u:object_r:initrc_devpts_t, not
> relabeling.Operation not permitted
> May 29 14:14:32 localhost su(pam_unix)[11876]: session closed for user
> interch
> May 29 14:14:32 localhost interchange: interchange startup succeeded
> May 29 14:14:38 localhost su(pam_unix)[11905]: session opened for user
> interch by sbronson(uid=0)
> May 29 14:14:38 localhost su[11905]: Warning!  Could not relabel
> /dev/pts/6 with user_u:object_r:initrc_devpts_t, not
> relabeling.Operation not permitted
> May 29 14:14:42 localhost su(pam_unix)[11905]: session closed for user
> interch
> May 29 14:14:52 localhost kernel: audit(1148937292.055:3812): avc:
> denied  { write } for  pid=11932 comm="store1" name="socket" dev=dm-0
> ino=1606292 scontext=root:system_r:httpd_sys_script_t
> tcontext=user_u:object_r:var_run_t tclass=sock_file
> 

Yup. You have a problem with SELinux. Either you will have to find
some way to enable writes to sockets via that, or just disable selinux
completely.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.765.647.1295  tollfree 800-949-1889 <mike at perusion.com>

Being against torture ought to be sort of a bipartisan thing.
-- Karl Lehenbauer


More information about the interchange-users mailing list