Discussion:
NW6.5SP5, PERL and Error message every time, when run Perl-Script
(too old to reply)
Serg
2006-02-19 12:13:07 UTC
Permalink
NW6.5SP5. Every time, when run Perl scrept i see this error message:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").

Why this and what can i do for resolver this ?

PS: on my NW6.5SP5 server:
LANGUAGE
Current NLM language is (4) ENGLISH.
Current DOS code page is (866).


Serg
Guenter Knauf, DevNet SysOp 32
2006-02-19 16:24:27 UTC
Permalink
Hi Serg,
thank you so much for posting that!! I gave exactly same....
I'm going nuts with that error!!

that's very strange, and something went wrong with the localisation...
my server is installed in English - but when I set 'language german' it
works and the error is gone!! Just ty if that fixes it for you too, f.e.
with 'language russian'...

Guenter.
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
Why this and what can i do for resolver this ?
LANGUAGE
Current NLM language is (4) ENGLISH.
Current DOS code page is (866).
Serg
Randolf Richardson
2006-02-19 18:31:49 UTC
Permalink
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
[sNip]

Are you running the script directly from the System Console, or is Apache
calling it (with, or without, ModPerl)?
--
Randolf Richardson - ***@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Vancouver, British Columbia, Canada
http://www.inter-corporate.com/

This message originated from within a secure, reliable,
high-performance network ... a Novell NetWare network.
Guenter Knauf, DevNet SysOp 32
2006-02-19 20:47:04 UTC
Permalink
Hi Randy,
Post by Randolf Richardson
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
[sNip]
Are you running the script directly from the System Console, or is Apache
calling it (with, or without, ModPerl)?
from Console -but doesnt matter since I see other NLMs also affeccted;
just give it a try self:
I guess as canadian you could have servers with cp850 or such, probably with
french ones; switch server language to english and test...

Guen.
Randolf Richardson
2006-02-20 17:00:33 UTC
Permalink
[sNip]
Post by Guenter Knauf, DevNet SysOp 32
Post by Randolf Richardson
Are you running the script directly from the System Console, or is Apache
calling it (with, or without, ModPerl)?
from Console -but doesnt matter since I see other NLMs also affeccted;
I guess as canadian you could have servers with cp850 or such, probably with
french ones; switch server language to english and test...
I don't. I normally pick U.S. English for Amercian-made products, or
Canadian English (or U.K. English if Canadian English isn't an option).

A long time ago in the days when MS-DOS 4.01 was the great new advancement
in the computing world and NetWare 2.x was the defacto standards for
computing networks, I developed a habit of choosing "U.S. English" as the
default/preferred language for all products that were produced in the USA
in order to avoid having to deal with strange problems.

My bad experiences with choosing non-US languages (such as Canadian
English) with many products that originated in the US lead to a
significant discovery for me that using US English for these products
resulted in the elimination of a lot of bugs or silly "message not
defined" messages popping up on the screen. Since then, I've always just
kept up the habit.

Of course, my preference is to use Canadian English whenever possible, but
only if I have time to test it. For products made in Canada, the U.K.,
etc., this just hasn't been a problem, of course.

With regards to French, that seems to be a common misconception about us
Canadians -- Frensh is very uncommon in Western Canada (Quebec, where
French is extremely common, is in Eastern Canada), and yet I find myself
conversing-in/reading/writing Chinese (Mandarin) on a daily basis.

Nearly all Canadians I know don't speak French at all, yet it is
interesting that many people from other countries assume that every
Canadian speaks it fluently. French is still taught in public school
though (which is probably one of the reasons so many people think we all
speak French), and I think this is definitely a good thing because the
understanding of more languages is certainly beneficial to everyone (and
most Canadians I know also share this view).
--
Randolf Richardson - ***@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Vancouver, British Columbia, Canada
http://www.inter-corporate.com/

This message originated from within a secure, reliable,
high-performance network ... a Novell NetWare network.
Guenter Knauf, DevNet SysOp 32
2006-02-20 21:06:59 UTC
Permalink
Hi Randy,
Post by Randolf Richardson
I don't. I normally pick U.S. English for Amercian-made products, or
Canadian English (or U.K. English if Canadian English isn't an option).
A long time ago in the days when MS-DOS 4.01 was the great new
advancement in the computing world and NetWare 2.x was the defacto
standards for computing networks, I developed a habit of choosing "U.S.
English" as the default/preferred language for all products that were
produced in the USA in order to avoid having to deal with strange
problems.
just me too. But its recommended - and worked all the time together - to
use cp850 instead of cp437, and I did use cp850 all the time togethe with
server language english.
Post by Randolf Richardson
My bad experiences with choosing non-US languages (such as Canadian
English) with many products that originated in the US lead to a
significant discovery for me that using US English for these products
resulted in the elimination of a lot of bugs or silly "message not
defined" messages popping up on the screen. Since then, I've always
just kept up the habit.
just me too.
Unfortunately NetWare did change its habit with SP5, and now forces me to
switch to German for whatever reason....

Guen.
Serg
2006-02-20 09:23:08 UTC
Permalink
Post by Randolf Richardson
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
[sNip]
Are you running the script directly from the System Console, or is Apache
calling it (with, or without, ModPerl)?
Run script direct from server console (not from apache).
Serg
Allan Brehm Clausen
2006-03-02 15:03:37 UTC
Permalink
I have the same problem on a CP850 English 6.5 sp5 machine.
How do I get rid of it?
Using the LANGUAGE command changes nothing, and trying to set the
LC_ALL and LANG environment variables also changes nothing.

Is it a general SP5 problem? Is the whole server affected?
I know it does it on my Branch Office 2.0.5 prebuild also, and thats
installed by Novell.

Is someone going to spend an incident on this? :-)

Regards
Allan
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
Why this and what can i do for resolver this ?
LANGUAGE
Current NLM language is (4) ENGLISH.
Current DOS code page is (866).
Serg
Guenter
2006-03-02 18:51:00 UTC
Permalink
Hi Allan,
yeah, I will try again....; really nasty issue...
however for me it worked to set to my native language - even though I did
not install german at all - only cp850 and keyboard driver, that's it...
I'll be back if I get more info.

Guenter.
Post by Allan Brehm Clausen
I have the same problem on a CP850 English 6.5 sp5 machine.
How do I get rid of it?
Using the LANGUAGE command changes nothing, and trying to set the
LC_ALL and LANG environment variables also changes nothing.
Is it a general SP5 problem? Is the whole server affected?
I know it does it on my Branch Office 2.0.5 prebuild also, and thats
installed by Novell.
Is someone going to spend an incident on this? :-)
Regards
Allan
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
Why this and what can i do for resolver this ?
LANGUAGE
Current NLM language is (4) ENGLISH.
Current DOS code page is (866).
Serg
Guenter
2006-03-07 16:55:34 UTC
Permalink
Hi,
Post by Guenter
Hi Allan,
yeah, I will try again....; really nasty issue...
however for me it worked to set to my native language - even though I did
not install german at all - only cp850 and keyboard driver, that's it...
I'll be back if I get more info.
I've just got a fixed LibC, and it looks good so far; the Perl warning is
gone, and another program which refused to work because of the locale stuff
also started again.....
however it needs more testing, and I cant tell at the moment if and when a
field test goes out - however I expect very soon....
if someone cant wait for updates, or is willing to help with testing, then
you can contact me privately through my board:
http://www.gknw.de/phpbb
either sign up and send me an internal mail though the system with your
request, and an address for sending the fix, or just use the contact forum -
however then all others can also see aour email which is probably not what
you want.

greets, Guenter.
Hartfiel
2006-03-28 19:57:15 UTC
Permalink
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
Why this and what can i do for resolver this ?
LANGUAGE
Current NLM language is (4) ENGLISH.
Current DOS code page is (866).
Serg
Hello Serg,

i've used the latest NW65SP5ISO Image and installed a brand new HP
Proliant DL380 from the scratch. Had exactly the same perl error (and
found your posting). I've installed nwlib6f.exe(beta) library and the
error message went away. Perl works for now.
But i have another issue since then. All the time the server is restarted
it's hanging at perl.nlm for about 1-2 minutes. Can`t find any error
message on the logger screen. Saw this behavior also on other NW65SP5
servers and on servers which were updated to SP5. Do you know how to
pinpoint this issue?

Regards,

Heinz
Serg
2006-03-29 08:11:51 UTC
Permalink
I`m sorry - do not know :(

Serg
Post by Hartfiel
Post by Serg
perl: warning: Setting locale failed.
LC_ALL = (unset),
LANG = (unset)
are supported and installed on your system.
perl: warning: Failling back to the standart locale ("C").
Why this and what can i do for resolver this ?
LANGUAGE
Current NLM language is (4) ENGLISH.
Current DOS code page is (866).
Serg
Hello Serg,
i've used the latest NW65SP5ISO Image and installed a brand new HP
Proliant DL380 from the scratch. Had exactly the same perl error (and
found your posting). I've installed nwlib6f.exe(beta) library and the
error message went away. Perl works for now.
But i have another issue since then. All the time the server is restarted
it's hanging at perl.nlm for about 1-2 minutes. Can`t find any error
message on the logger screen. Saw this behavior also on other NW65SP5
servers and on servers which were updated to SP5. Do you know how to
pinpoint this issue?
Regards,
Heinz
Loading...