[ic] Interchange server is unavailable... emergency

[David Christensen]

On Dec 29, 2009, at 12:48 PM, Gert van der Spoel wrote:

>> -----Original Message-----
>> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
>> users-bounces at icdevgroup.org] On Behalf Of Rick Bragg
>> Sent: Monday, December 28, 2009 12:14 PM
>> To: interchange-users at icdevgroup.org
>> Subject: Re: [ic] Interchange server is unavailable... emergency
>>
>> On Mon, 2009-12-28 at 11:04 +0200, Gert van der Spoel wrote:
>>>> -----Original Message-----
>>>> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
>>>> users-bounces at icdevgroup.org] On Behalf Of Rick Bragg
>>>> Sent: Monday, December 28, 2009 10:39 AM
>>>> To: interchange-users at icdevgroup.org
>>>> Subject: Re: [ic] Interchange server is unavailable... emergency
>>>>
>>>> On Mon, 2009-12-28 at 03:24 -0500, Rick Bragg wrote:
>>>>> Hi,
>>>>>
>>>>> I have quite an emergency, Any help will be greatly appreciated!
>>>>>
>>>>> I have an IC install on the temphost.net server at Endpoint,
>> under
>>>>> "montp" and for some reason the server is giving me the following
>>>>> 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.
>>>>>
>>>>> The only thing I did was add a few tables to the mysql database
>> via
>>>>> direct sql query. surveys, survey_questions, survey_answers, and
>>>>> survey_results.  I also added the corresponding ###.mysql, files
>> to
>>>> the
>>>>> catalogs' dbconf/mysql/ directory and the corresponding
>>>> products/###.txt
>>>>> files, and touched the corresponding products/.###.sql files
>>>>>
>>>>> I can't see anything in the logs at all.  The server is running
>> as
>>>> far
>>>>> as I can tell. Here is some info:
>>>>>
>>>>>
>>>>> $ netstat  -a | grep montp
>>>>> unix  2      [ ACC ]     STREAM     LISTENING     365214003
>>>> /home/montp/interchange/etc/socket.ipc
>>>>> unix  2      [ ACC ]     STREAM     LISTENING     365214005
>>>> /home/montp/interchange/etc/socket
>>>>> unix  2      [ ]         STREAM     CONNECTED     365214023
>>>> /home/montp/interchange/etc/socket.ipc
>>>>>
>>>>> $ ps aux |grep montp
>>>>> ...
>>>>> montp     8353  0.0  0.0 110908  3608 pts/13   S+   Oct05   0:00
>>>> mysql montp
>>>>> montp    17842  0.0  0.0  66208  1688 pts/9    Ss   Dec09   0:00
>> -
>>>> bash
>>>>> montp    17900  0.0  0.0 110860  3680 pts/9    S+   Dec09   0:00
>>>> mysql
>>>>> montp    21737  0.0  0.4 245088 59440 ?        Ss   02:02   0:00
>>>> interchange: /home/montp/interchange
>>>>> montp    21739  0.0  0.4 245088 59192 ?        S    02:02   0:00
>>>> interchange: /home/montp/interchange
>>>>> montp    21740  0.0  0.4 245088 59192 ?        S    02:02   0:00
>>>> interchange: /home/montp/interchange
>>>>> ...
>>>>>
>>>>> $ re
>>>>> Killing Interchange server 21737 with TERM.
>>>>> Vend::Payment::AuthorizeNet payment module initialized, using LWP
>> and
>>>> Crypt::SSLeay
>>>>> Vend::Payment::TestPayment payment module loaded
>>>>> Sending debug messages to debug.log.
>>>>> RPC traffic settings.
>>>>> Calling UI......UI is loaded...
>>>>> Interchange V5.6.2
>>>>> Running with old signals.
>>>>> Configuring catalog montpelier...Using MySQL,
>>>> DSN=dbi:mysql:montp...done.
>>>>> Interchange server started in UNIX mode(s) (process id 22909)
>>>>>
>>>>>
>>>>> Thanks
>>>>> Rick
>>>>>
>>>>
>>>>
>>>> More info:
>>>>
>>>> # strings /var/www/cgi-bin/montpelier-vt.org/municode |grep soc
>>>> socket
>>>> etc/sockH
>>>> Could not open socket
>>>>
>>>> This is it, I can't tell if by adding database tables caused this
>> or
>>>> not
>>>> since I didn't open a browser until after I updated the database.
>> I
>>>> think that it is totally unrelated...
>>>>
>>>> What can I do to fix this?
>>>
>>> Have you tried to login to the database on the commandline and see  
>>> if
>> the
>>> tables have been created?
>>>
>>> CU,
>>>
>>> Gert
>>>
>>
>> The database has now been rolled back to the way it was before I knew
>> anything about the problem,  Also removed the .mysql .txt and .sql
>> files.  That should rule out the problem being from the database.   
>> Also
>> permissions on the socket were checked, Still no go...
>
> I noticed the site is back up ... Got any info on what the problem was
> eventually?

I believe this had been an SELinux issue with the socket.

Regards,

David
--
David Christensen
End Point Corporation
david at endpoint.com