[ic] Interchange crashing when updating order status in admin.

[Cameron G]

> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org 
> [mailto:interchange-users-bounces at icdevgroup.org] On Behalf 
> Of Joachim Leidinger
> Sent: Monday, October 20, 2003 3:49 AM
> To: interchange-users at icdevgroup.org
> Subject: Re: [ic] Interchange crashing when updating order 
> status in admin.
> 
> Cameron G wrote:
> ....
> >>This looks like you are running your userdb on GDBM or some other 
> >>non-SQL database. Not recommended, especially for busy sites. 
> >>Interchange does a lot of database updates in the latest foundation 
> >>catalogs, and if you have a lot of logged-in users this can easily 
> >>happen.
> >>
> >>It probably means you are getting caught up in write 
> contention that 
> >>can't be resolved.
> >>
> >>Try switching the userdb, transactions, and orderline tables to SQL 
> >>and see what happens then.
> >>
> >>
> > 
> > 
> > I already am running on mysql, and have been for several 
> months now. 
> > :/
> ....
> 
> Any messages in the error.log files of IC?
> 
> Joachim
> 
> --

Other than the: 

- - - [17/October/2003:02:50:55 -0600] - - Spurious PID file for process
7456 supposedly running 300 seconds
- - - [17/October/2003:02:52:18 -0600] - - Spurious PID file for process
7558 supposedly running 302 seconds
- - - [17/October/2003:02:52:45 -0600] - - Spurious PID file for process
7571 supposedly running 301 seconds
- - - [17/October/2003:02:53:15 -0600] - - Spurious PID file for process
7576 supposedly running 301 seconds
- - - [17/October/2003:02:54:15 -0600] - - Spurious PID file for process
7696 supposedly running 302 seconds
- - - [17/October/2003:02:55:03 -0600] - - Spurious PID file for process
7716 supposedly running 301 seconds
- - - [17/October/2003:22:36:49 -0600] - - hammered PID 30856 running 300
seconds
- - - [17/October/2003:22:37:23 -0600] - - hammered PID 30885 running 302
seconds
- - - [17/October/2003:22:40:21 -0600] - - hammered PID 31020 running 301
seconds

Error of a child process that's misbehaving, no. :(