Hi Michiel,

I tried the $SERVERTIMESTAMP$ but it returns the client time instead of
the server time.

Emily

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Michiel Beijen
Sent: Thursday, March 29, 2007 1:10 AM
To: [email protected]
Subject: Re: $PROCESS$

Emily,

Of course you have an issue with this $PROCESS$ command. But I just
wanted to point out that in version 6 there is no need to fetch the
time like this, please take a look at the $SERVERTIMESTAMP$ keyword. I
guess this will also do what you try to achieve.

-- 
Met vriendelijke groet / Kind regards
Michiel Beijen
______________________________________________________
MANSOLUTIONS
Energieweg 60-62
3771 NA Barneveld
The Netherlands
Tel. +31-(0)612968592
Mail [EMAIL PROTECTED]
Internet http://bsm.mansolutions.nl


On 3/29/07, Chao, Emily <[EMAIL PROTECTED]> wrote:
> For the storage arrangement, I need to check our Unix admin and get
back
> to you tomorrow.
>
> I don't see anything in the /var/log/messages.
>
> -rw-------    1 root     root            0 Mar 25 04:02 messages
>
> Here's the output:
>
> # ulimit -a
> address space limit (kbytes)   (-M)  unlimited
> core file size (blocks)        (-c)  0
> cpu time (seconds)             (-t)  unlimited
> data size (kbytes)             (-d)  unlimited
> file size (blocks)             (-f)  unlimited
> locks                          (-L)  unlimited
> locked address space (kbytes)  (-l)  4
> nofile                         (-n)  1024
> nproc                          (-u)  7168
> pipe buffer size (bytes)       (-p)  4096
> resident set size (kbytes)     (-m)  unlimited
> socket buffer size (bytes)     (-b)  4096
> stack size (kbytes)            (-s)  10240
> threads                        (-T)  not supported
> process size (kbytes)          (-v)  unlimited
>
>
>
> # ps -ef|grep arserverd
> root      9724  9721  0 02:37 pts/2    00:00:13 /var/ar/bin/arserverd
-s
> arserver -i /var/ar -l /etc/arsystem/arserver
> root     12263  9314  0 04:13 pts/2    00:00:00 grep arserverd
> # lsof -p 9724 | wc -l
>       71
>
> Thank you so much for looking into this!
> Emily
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Axton
> Sent: Wednesday, March 28, 2007 8:34 PM
> To: [email protected]
> Subject: Re: $PROCESS$
>
> The best advice I can give at this point is to turn on the fork logs
> and see if there is any additional information there.  I suspect that
> what you are seeing presently is all the logs will show, which tells
> me that there is a bad block on the storage device in use.  What is
> the storage arrangement on the server (mirrored, single drive, etc.)?
>
> Try looking in /var/log/messages to see if you are hitting any type of
> limit.  Can you post the output of ulimit -a?  It should look
> something like:
>
> [EMAIL PROTECTED] ~]$ ulimit -a
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 1024
> max locked memory       (kbytes, -l) 32
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> stack size              (kbytes, -s) 10240
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 137216
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
>
> You can check the number of file descriptors in use by a process
using:
> lsof -p <pid> | wc -l
>
> Make sure this is not at the limit when you receive the error.
>
> Axton Grams
>
> On 3/28/07, Chao, Emily <[EMAIL PROTECTED]> wrote:
> > Hi Axton,
> >
> > Actually I am able to run the date command in the Linux server.
> >
> > When I stop and start the ARS and try my AL, it will work and return
> the
> > server time once in the field. Did another test after that, it's not
> > working again. The field returns no value. Then I see the below
> message
> > pop up in the console.
> >
> > [1] +  Done                    ./arsystem start &
> > # date: write error: Bad file descriptor
> >
> > Any idea?
> >
> > Thank you,
> > Emily
> >
> > -----Original Message-----
> > From: Action Request System discussion list(ARSList)
> > [mailto:[EMAIL PROTECTED] On Behalf Of Axton
> > Sent: Wednesday, March 28, 2007 5:44 PM
> > To: [email protected]
> > Subject: Re: $PROCESS$
> >
> > Run fsck on your linux server.
> >
> > [EMAIL PROTECTED] ~]$ uname -a
> > Linux arswiki.org 2.6.9-023stab041.3-enterprise #1 SMP Wed Feb 14
> > 13:36:44 MSK 2007 i686 i686 i386 GNU/Linux
> > [EMAIL PROTECTED] ~]$ cat /etc/redhat-release
> > CentOS release 4.4 (Final)
> > [EMAIL PROTECTED] ~]$ date '+%m/%d/%y %H:%M:%S'
> > 03/28/07 20:40:58
> >
> > Axton Grams
> >
> > On 3/28/07, Chao, Emily <[EMAIL PROTECTED]> wrote:
> > > **
> > >
> > >
> > >
> > > Hi List,
> > >
> > >
> > >
> > > I have an active link with the following syntax. I need to get the
> > server
> > > date/time and return the value into a character field. There is no
> > problem
> > > in the 5.1 on Solaris machine using this command in an AL. After
> > upgrading
> > > in 6.3 on a Linux box, I got "date: write error: Bad file
> descriptor"
> > error
> > > from my SSH console.
> > >
> > >
> > >
> > > $PROCESS$ @@:date '+%m/%d/%y %H:%M:%S'
> > >
> > >
> > >
> > > ARS: 6.3 Patch21
> > >
> > > DB: Oracle 10g
> > >
> > > OS: Linux Red Hat 3
> > >
> > >
> > >
> > > Any input would be greatly appreciated.
> > >
> > > Thank you,
> > >
> > >
> > >
> > > Emily Chao
> > >
> > > [EMAIL PROTECTED]
> > >
> > > AboveNet, Inc.
> > >
> > > Remedy Administrator
> > >
> > >   __20060125_______________________This posting was
> > > submitted with HTML in it___
> >
> >
>
________________________________________________________________________
> > _______
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> ARSlist:"Where
> > the Answers Are"
> >
> >
>
________________________________________________________________________
> _______
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> ARSlist:"Where the Answers Are"
> >
>
>
________________________________________________________________________
> _______
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where
> the Answers Are"
>
>
________________________________________________________________________
_______
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where the Answers Are"
>

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to