Tim,

 

It's a good question, and at least right now, I can say the answer is no.  Normally, when iChain sees that one of the backend servers is down, it will not try to use it for anything.  However, with all the weird stuff that was going on since yesterday, we started wondering the same thing that you did, so we manually removed the broken server out of the iChain configuration. 

 

I see two possibilities here.  One is that we installed two new extensions yesterday and one of them is causing problems.  The other, and probably most likely, is that this has always happened and it is only noticeable when trying to do an import.  Any other ideas, anyone?

 

>>> Tim Mohlmann <muhlemmer@gmail.com> 7/14/2010 11:37 AM >>>
>Not an expert but... is iChain still trying to log in users on the
>broken server? Dividing load or something. Login being a secure
>connection, so a different port then ordinary traffic, so might be in
>different config? Something like that.
>
>2010/7/14 Matthew Ehle <mehle@novell.com>:
> There appears to be some kind of bug in the login script.  When I was
> getting the error, I noticed that the logs kept indicating that I was logged
> in iChain, but not in the wiki.  Normally, it should only give that message
> once.  This means that for whatever reason, I was not being automatically
> logged into the wiki, hence the error.  When I log out and back in, the
> message appears only appears once, meaning that I managed to get logged into
> the wiki.  Any ideas on what might be going on there?
>
>>>> Juergen Weigert <jw@suse.de> 7/14/2010 11:19 AM >>>
> On Jul 14, 10 10:54:12 -0600, Matthew Ehle wrote:
>> The hardware failure yesterday really threw iChain for a loop.  After
>> getting random reports of slowness, we reconfigured and cleared out the
>> some things in iChain. Since iChain handles session data, it is possible
>> that is what is causing your problem.
>>
>> Can anyone else duplicate this?
>
>>I have had several 'Loss of session data.' errors. This was during
>>normal editing. Most of the time it helped to hit save multiple times.
>>I saw it ca 5 hours ago, when repeated save did not help.
>>
>>The wiki appears to be exceptioanlly slow today.
>>Firebug tells me that the reload from clicking the logout button takes
>>29.53 seconds 'Waiting for Response'
>>
>>        cheers,
>>                JW-
> Could you please more specific?  Which wiki(s) and page(s)?  If it's only
> the logout that is taking a long time, that would be an iChain issue that I
> need to pass on.  If it's more than that, I will have to try to get as much
> information as possible.
>
>> Pistazienfresser, can you try again
>> after starting a new session, clearing your cookies, etc.?
>>
>> Thanks,
>> Matt
>>
>> >>>> pistazienfresser <pistazienfresser@gmx.de> 7/14/2010 10:42 AM >>>
>> >Hello wiki-list,
>> >
>> >I have tried now several times to import an article with history but
>> >every time I get an message about a loss of session data.
>> >
>> >Greetings
>> >pistazienfresser
>> >
>> >--
>> >
>> >- openSUSE profile: https://users.opensuse.org/show/pistazienfresser
>> >--
>> >To unsubscribe, e-mail: opensuse-wiki+unsubscribe@opensuse.org
>> >For additional commands, e-mail: opensuse-wiki+help@opensuse.org
>>
>
> --
> o \  Juergen Weigert  paint it green!    __/ _=======.=======_
> <V> | jw@suse.de       back to ascii!  __/        _---|____________\/
> \  | 0911 74053-508                __/          (____/            /\
> (/) | _____________________________/              _/ \_ vim:set sw=2 wm=8
> SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
> "You are trying to use packages from project 'openSUSE:11.2'.
> Note that malicious packages can compromise your system."
>
>