sql-ledger-users

[SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi List 

SQL Version 2.6.19 has been acting up since the last upgrade.  We have
to keep inputting our password all the time.

Cheers List


-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Paul T. <pt...@wa...>]

Chuck Amadi Systems Administrator schreef:
> Hi List 
>
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
>
> Cheers List
>
>
>   
use admin.pl to set user defaults for time-out to higher standards might 
be a solution?

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi Paul

Thanks for your tip

But the Session Timeout is set as default which is 3600 seconds (1hour).
Unfortunately for me as SysAdmin there session expires well before 3600
seconds.

I have gooogled around (looking at my docs)but no joy So I will continue
my search for a remedy
before utilising my paid up support with Dieter.

Cheers

On Wed, 2006-11-15 at 13:39 +0100, Paul Tammes wrote:
> Chuck Amadi Systems Administrator schreef:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> use admin.pl to set user defaults for time-out to higher standards might 
> be a solution?
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Dieter S. <dsi...@sq...>]

The session timeout when you log in to admin.pl is preset at 600 seconds.
This cannot be changed unless you change the code.

The user's timeout value can be set to any value. If frequent timeouts
occur try something like 86400 (1 day). This will take care of problems
with GMT between browser and server as well as daylight savings time
differences.


-- 
Dieter Simader       http://www.sql-ledger.com   Tel: (780) 472-8161
DWS Systems Inc.        Accounting Software      Fax: (780) 478-5281
============== On a clear disk you can seek forever ================

On Wed, 15 Nov 2006, Chuck Amadi Systems Administrator wrote:

> Hi Paul
>
> Thanks for your tip
>
> But the Session Timeout is set as default which is 3600 seconds (1hour).
> Unfortunately for me as SysAdmin there session expires well before 3600
> seconds.
>
> I have gooogled around (looking at my docs)but no joy So I will continue
> my search for a remedy
> before utilising my paid up support with Dieter.
>
> Cheers
>
> On Wed, 2006-11-15 at 13:39 +0100, Paul Tammes wrote:
> > Chuck Amadi Systems Administrator schreef:
> > > Hi List
> > >
> > > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > > to keep inputting our password all the time.
> > >
> > > Cheers List
> > >
> > >
> > >
> > use admin.pl to set user defaults for time-out to higher standards might
> > be a solution?
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > sql-ledger-users mailing list
> > sql...@li...
> > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> >
>

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi Dieter

Cheers for the reply - Richard's advise about checking my sl server's
time and the clients accessing SL time where the factor 20 mins
difference.

ntpd had stopped!.

Thus started ntp client on the sl server which was 20 mins behind the
clients and my watch.

Cheers all 

On Wed, 2006-11-15 at 08:14 -0700, Dieter Simader wrote:
> The session timeout when you log in to admin.pl is preset at 600 seconds.
> This cannot be changed unless you change the code.
> 
> The user's timeout value can be set to any value. If frequent timeouts
> occur try something like 86400 (1 day). This will take care of problems
> with GMT between browser and server as well as daylight savings time
> differences.
> 
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Dave S. <bou...@ya...>]

I've noticed since going to to 2.6.19 that there have
been some timeout issues too.  Many days I'll logon
and then immediatly be presented with a timeout /
please logon screen.  I've also gotten (for the first
time) with this version occasionally the requirement
to enter a logon password to both the menu frame and
the main frame.

Dave
--- Dieter Simader <dsi...@sq...> wrote:

> The session timeout when you log in to admin.pl is
> preset at 600 seconds.
> This cannot be changed unless you change the code.
> 
> The user's timeout value can be set to any value. If
> frequent timeouts
> occur try something like 86400 (1 day). This will
> take care of problems
> with GMT between browser and server as well as
> daylight savings time
> differences.
> 
> 
> -- 
> Dieter Simader       http://www.sql-ledger.com  
> Tel: (780) 472-8161
> DWS Systems Inc.        Accounting Software     
> Fax: (780) 478-5281
> ============== On a clear disk you can seek forever
> ================
> 
> On Wed, 15 Nov 2006, Chuck Amadi Systems
> Administrator wrote:
> 
> > Hi Paul
> >
> > Thanks for your tip
> >
> > But the Session Timeout is set as default which is
> 3600 seconds (1hour).
> > Unfortunately for me as SysAdmin there session
> expires well before 3600
> > seconds.
> >
> > I have gooogled around (looking at my docs)but no
> joy So I will continue
> > my search for a remedy
> > before utilising my paid up support with Dieter.
> >
> > Cheers
> >
> > On Wed, 2006-11-15 at 13:39 +0100, Paul Tammes
> wrote:
> > > Chuck Amadi Systems Administrator schreef:
> > > > Hi List
> > > >
> > > > SQL Version 2.6.19 has been acting up since
> the last upgrade.  We have
> > > > to keep inputting our password all the time.
> > > >
> > > > Cheers List
> > > >
> > > >
> > > >
> > > use admin.pl to set user defaults for time-out
> to higher standards might
> > > be a solution?
> > >
> > >
>
-------------------------------------------------------------------------
> > > Take Surveys. Earn Cash. Influence the Future of
> IT
> > > Join SourceForge.net's Techsay panel and you'll
> get the chance to share your
> > > opinions on IT & business topics through brief
> surveys - and earn cash
> > >
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > _______________________________________________
> > > sql-ledger-users mailing list
> > > sql...@li...
> > >
>
https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> > >
> >
> 
> 
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
>
https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> 



 
____________________________________________________________________________________
Sponsored Link

Mortgage rates near 39yr lows. 
$510k for $1,698/mo. Calculate new payment! 
www.LowerMyBills.com/lre

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi Again

Just to recap my issue was most definitely a ntp issue.

The SL Finance server ntp daemon had died and it lost over a period of
time
when I had done the last update 20 mins and the Clients which are on a
Windows domain and had the correct time where via the web interface
having session expiry issues after clicking 4 or 5 times.

After restarting ntp daemon and thus monitoring  for a short while all
was back to normal.

Cheers

Chuck

On Thu, 2006-11-16 at 20:27 -0800, Dave Snell wrote:
> I've noticed since going to to 2.6.19 that there have
> been some timeout issues too.  Many days I'll logon
> and then immediatly be presented with a timeout /
> please logon screen.  I've also gotten (for the first
> time) with this version occasionally the requirement
> to enter a logon password to both the menu frame and
> the main frame.
> 
> Dave
> --- Dieter Simader <dsi...@sq...> wrote:
> 
> > The session timeout when you log in to admin.pl is
> > preset at 600 seconds.
> > This cannot be changed unless you change the code.
> > 
> > The user's timeout value can be set to any value. If
> > frequent timeouts
> > occur try something like 86400 (1 day). This will
> > take care of problems
> > with GMT between browser and server as well as
> > daylight savings time
> > differences.
> > 
> > 
> > -- 
> > Dieter Simader       http://www.sql-ledger.com  
> > Tel: (780) 472-8161
> > DWS Systems Inc.        Accounting Software     
> > Fax: (780) 478-5281
> > ============== On a clear disk you can seek forever
> > ================
> > 
> > On Wed, 15 Nov 2006, Chuck Amadi Systems
> > Administrator wrote:
> > 
> > > Hi Paul
> > >
> > > Thanks for your tip
> > >
> > > But the Session Timeout is set as default which is
> > 3600 seconds (1hour).
> > > Unfortunately for me as SysAdmin there session
> > expires well before 3600
> > > seconds.
> > >
> > > I have gooogled around (looking at my docs)but no
> > joy So I will continue
> > > my search for a remedy
> > > before utilising my paid up support with Dieter.
> > >
> > > Cheers
> > >
> > > On Wed, 2006-11-15 at 13:39 +0100, Paul Tammes
> > wrote:
> > > > Chuck Amadi Systems Administrator schreef:
> > > > > Hi List
> > > > >
> > > > > SQL Version 2.6.19 has been acting up since
> > the last upgrade.  We have
> > > > > to keep inputting our password all the time.
> > > > >
> > > > > Cheers List
> > > > >
> > > > >
> > > > >
> > > > use admin.pl to set user defaults for time-out
> > to higher standards might
> > > > be a solution?
> > > >
> > > >
> >
> -------------------------------------------------------------------------
> > > > Take Surveys. Earn Cash. Influence the Future of
> > IT
> > > > Join SourceForge.net's Techsay panel and you'll
> > get the chance to share your
> > > > opinions on IT & business topics through brief
> > surveys - and earn cash
> > > >
> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > > _______________________________________________
> > > > sql-ledger-users mailing list
> > > > sql...@li...
> > > >
> >
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> > > >
> > >
> > 
> > 
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get
> > the chance to share your
> > opinions on IT & business topics through brief
> > surveys - and earn cash
> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > sql-ledger-users mailing list
> > sql...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> > 
> 
> 
> 
>  
> ____________________________________________________________________________________
> Sponsored Link
> 
> Mortgage rates near 39yr lows. 
> $510k for $1,698/mo. Calculate new payment! 
> www.LowerMyBills.com/lre
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Tom D. <td...@ro...>]

On Thu, 16 Nov 2006, Dave Snell wrote:

> I've noticed since going to to 2.6.19 that there have
> been some timeout issues too.  Many days I'll logon
> and then immediatly be presented with a timeout /
> please logon screen.  I've also gotten (for the first
> time) with this version occasionally the requirement
> to enter a logon password to both the menu frame and
> the main frame.

You are not the only one. Sometimes it gets into a loop and asks for
the passwd everytime I try to get another screen. logging into
BOTH the meny frame and the main frame seems to satisfy it.

FWIW ALL clocks on my local net are ntp synced and this problem
occurs frequently on my local desktop. The timeout is set for
9999999999999999999 and the browser is firefox.

Regards,

-- 
Tom Diehl		td...@ro...		Spamtrap address mt...@ro...

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Stroller <lin...@my...>]

On 17 Nov 2006, at 20:41, Tom Diehl wrote:
> On Thu, 16 Nov 2006, Dave Snell wrote:
>> I've noticed since going to to 2.6.19 that there have
>> been some timeout issues too.  Many days I'll logon
>> and then immediatly be presented with a timeout /
>> please logon screen. ...
>
> You are not the only one. Sometimes it gets into a loop and asks for
> the passwd everytime I try to get another screen. logging into
> BOTH the meny frame and the main frame seems to satisfy it.

I had this upon upgrading to 2.16.19, too.

> ...The timeout is set for
> 9999999999999999999 and the browser is firefox.

I seem to recall that I too had a silly timeout figure. It was either  
99999999999999 or 0 - setting it to comething like 3600 (in admin.pl  
 > username) resolved the issue for me.

Stroller.

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[C. D. H. <Du...@Du...>]

Stroller wrote:
> On 17 Nov 2006, at 20:41, Tom Diehl wrote:
>   
>> On Thu, 16 Nov 2006, Dave Snell wrote:
>>     
>>> I've noticed since going to to 2.6.19 that there have
>>> been some timeout issues too.  Many days I'll logon
>>> and then immediatly be presented with a timeout /
>>> please logon screen. ...
>>>       
>> You are not the only one. Sometimes it gets into a loop and asks for
>> the passwd everytime I try to get another screen. logging into
>> BOTH the meny frame and the main frame seems to satisfy it.
>>     
>
> I had this upon upgrading to 2.16.19, too.
>
>   
>> ...The timeout is set for
>> 9999999999999999999 and the browser is firefox.
>>     
>
> I seem to recall that I too had a silly timeout figure. It was either  
> 99999999999999 or 0 - setting it to comething like 3600 (in admin.pl  
>  > username) resolved the issue for me.
>   
My users are all either set to 14400 or 28800 - depending upon their job 
functions.  All of my users have complained about the "immediate 
relogin" issue since going to 2.6.19.

dunc

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Stroller <lin...@my...>]

On 19 Nov 2006, at 23:38, C. Duncan Hudson wrote:
> ...
> My users are all either set to 14400 or 28800 - depending upon  
> their job
> functions.  All of my users have complained about the "immediate
> relogin" issue since going to 2.6.19.

Just a thought - have you tried changing the users' timeout settings  
since the upgrade? Changing from 14400 to 14401 (and even back  
again!) might be worth a go - I have known applications to respond to  
that.

Ironically one of the demo installations of SL <http://neptune.sql- 
ledger.com/sql-ledger/> is exhibiting this problem.

Stroller.

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Tom D. <td...@ro...>]

On Sat, 18 Nov 2006, Stroller wrote:

>
> On 17 Nov 2006, at 20:41, Tom Diehl wrote:
>> On Thu, 16 Nov 2006, Dave Snell wrote:
>>> I've noticed since going to to 2.6.19 that there have
>>> been some timeout issues too.  Many days I'll logon
>>> and then immediatly be presented with a timeout /
>>> please logon screen. ...
>>
>> You are not the only one. Sometimes it gets into a loop and asks for
>> the passwd everytime I try to get another screen. logging into
>> BOTH the meny frame and the main frame seems to satisfy it.
>
> I had this upon upgrading to 2.16.19, too.
>
>> ...The timeout is set for
>> 9999999999999999999 and the browser is firefox.
>
> I seem to recall that I too had a silly timeout figure. It was either
> 99999999999999 or 0 - setting it to comething like 3600 (in admin.pl
> > username) resolved the issue for me.

But that still means you have to login every hour. I wish Dieter would have
a magic value that would disable the thing. It is annoying. I like the idea of
setting it to 0.

I understand it is desired/needed for some but in my environment it is simply
an annoyance.

Regards,

-- 
Tom Diehl		td...@ro...		Spamtrap address mt...@ro...

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Stroller <lin...@my...>]

On 18 Nov 2006, at 03:25, Tom Diehl wrote:
> ...
>> I seem to recall that I too had a silly timeout figure. It was either
>> 99999999999999 or 0 - setting it to comething like 3600 (in admin.pl
>>> username) resolved the issue for me.
>
> But that still means you have to login every hour.

Um.. only if you're not using it, of course. Try 36000 - 10 hours -  
instead, or whatever you like.

I honestly had this same problem when I upgraded from c 2.6.12 to  
2.6.19.

It was extremely annoying and the symptoms EXACTLY met the  
descriptions: "I'll logon and then immediatly be presented with a  
timeout / please logon screen" and "it gets into a loop and asks for  
the passwd everytime I try to get another screen. logging into BOTH  
the meny frame and the main frame seems to satisfy it."

My timeout was also set to a "silly" number - as many 99999999999999s  
as I could fit in the box, I think.

Setting the timeout to a more reasonable number resolved the issue  
for me.

If this is a problem for you, start by setting the timeout to an hour  
and then work upwards.

Even having to log in every hour cannot be worse than logging in and  
then getting the "session timeout, please log in" message on the very  
next page. I know how annoying this message is - I too have  
experienced it on a minutely basis.

> I wish Dieter would have a magic value that would disable the  
> thing. It is annoying...
> ...in my environment it is simply an annoyance.

Whining about the problem doesn't help. Documenting the problem and  
saying "the timeout setting works perfectly when it is set below 2^16  
seconds [1], but when it is set above this figure then the user  
experiences inappropriate session timeout messages & logon demands"  
allows people to actually diagnose the issue & maybe resolve it for you.

Stroller.



[1] or 65,536 seconds, 2^32 seconds, 3 hours, 4,294,967,296 seconds  
or whatever.

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Richard P. <ri...@he...>]

Chuck Amadi Systems Administrator wrote:
> Hi List 
>
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
>
> Cheers List
>
>
>   
If you have not changed your session time-outs then check that the time
on the server matches the time on your clients...

Regards

-- 

Richard Patterson          HelpQuick Limited
Tel: 0191 2582888          Fax: 0191 6408666
Jabber chat:  ri...@ja...
Web:     http://www.helpquick.co.uk

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi Unfortunamtly for me

The Linux finance Server is based at a remote office.

So I have spoken to a power user to admin the server and type the date
command
if the user is able to get a xterm prompt and to check her Windows
Client date/time clock if not I got a trip this afternoon.

I will thus restart the ntp daemon on the finance server.
So if there is any other checks I ca do please let me know So 
I am armed and dangerous when I pop out later.

Thanks

On Wed, 2006-11-15 at 12:53 +0000, Richard Patterson wrote:
> Chuck Amadi Systems Administrator wrote:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> If you have not changed your session time-outs then check that the time
> on the server matches the time on your clients...
> 
> Regards
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi 

The power user got back to me.

The Sever time was 12:53 and the Windows Client time was 13:11.

Can someone also explain if this is the possible causes
I will restart the ntp when I pop over there today.

Cheers

On Wed, 2006-11-15 at 12:53 +0000, Richard Patterson wrote:
> Chuck Amadi Systems Administrator wrote:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> If you have not changed your session time-outs then check that the time
> on the server matches the time on your clients...
> 
> Regards
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi List

Hi List

Richards tip was the clincher

On the finance sl server to look up or signal processes based on name I
run # pgrep ntpd - and there wasn't a process number

Thus used Yast > Network Services > NTP Client and check "When booting
System"
and check the ntp servers ntp0.ISP.net ntp1.ISP.net and ntp2.ISP.net
Thus run # ntpq -p and thus the SL power users where able to click to
their hearts content as prior to this it was 4 or 5 clicks.

Cheers


On Wed, 2006-11-15 at 12:53 +0000, Richard Patterson wrote:
> Chuck Amadi Systems Administrator wrote:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> If you have not changed your session time-outs then check that the time
> on the server matches the time on your clients...
> 
> Regards
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi List Sorry but I forgot to mention their using IE6
SL is installed on a Linux SLES 9 Server But the user access
SL and Postgresql via IE Browser web interface.

SQL Version 2.6.19 has been acting up since the last upgrade.  We have
to keep inputting our password all the time.

PS Thus I gather it's a possible cache issue Please email suggestions or
good links

Cheers List


On Wed, 2006-11-15 at 12:21 +0000, Chuck Amadi Systems Administrator
wrote:
> Hi List 
> 
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
> 
> Cheers List
> 
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi List

I note that a lot of SQL Admins and their users had session expiry
issues.
I did get to the bottom of mine which was due to ntp daemon dieing on me
somehow nevertheless I just had to restart ntpd and the server and
clients where in harmony.

I have since upgraded to version 2.6.20 after updating our test site and
all is well nice to see how many suggestions and possible fixes were
sent and thanks Dieter for your quick response.

Cheers

Chuck

On Wed, 2006-11-15 at 12:28 +0000, Chuck Amadi Systems Administrator
wrote:
> Hi List Sorry but I forgot to mention their using IE6
> SL is installed on a Linux SLES 9 Server But the user access
> SL and Postgresql via IE Browser web interface.
> 
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
> 
> PS Thus I gather it's a possible cache issue Please email suggestions or
> good links
> 
> Cheers List
> 
> 
> On Wed, 2006-11-15 at 12:21 +0000, Chuck Amadi Systems Administrator
> wrote:
> > Hi List 
> > 
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> > 
> > Cheers List
> > 
> > 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830