OttoM,
I did as requested. The result was one file (
/var/opt/SUNWut/tmp/admincgi-truss.5690 ) which was empty.
Mike
=============================================
On 12/13/06, Mike Jones <[EMAIL PROTECTED]> wrote:
Dec 13 17:01:24 bobcat-1 login[9046]: [ID 521130 user.info] utadt::
username={admin} hostname={bobcat-1} service={Admin} cmd={}
message={Logged in user "admin" from server 24.180.37.182 into Admin
GUI} status={0} return_val={0}
Dec 13 17:01:37 bobcat-1 admincgi[9158]: [ID 702911 user.info] Error
opening status file
(bobcat-1)# ls -lnd /var/opt/SUNWut/tmp
drwxrwx--- 4 0 3001 13312 Dec 13 14:48
/var/opt/SUNWut/tmp
(bobcat-1)# ls -lnd /etc/opt/SUNWut/utadmin.pw
-rw-rw---- 1 0 3001 10 Dec 9 16:14
/etc/opt/SUNWut/utadmin.pw
(bobcat-1)# /bin/id utwww
uid=890(utwww) gid=3001(utadmin)
That all looks fine, unfortunately.
If this was happening to me then my next step would be to run the
CGI program under 'truss' to get a better picture of what's going on.
If you're up for that then do this on bobcat-1:
cd /opt/SUNWut/cgi-bin
mv admincgi admincgi.bin
echo '#! /bin/sh' > admincgi
echo ' /usr/bin/truss -o /var/opt/SUNWut/tmp/admincgi-truss.$$
/opt/SUNWut/cgi-bin/admincgi-bin "$@" ' >> admincgi
chmod a+rx admincgi
Then log in to the web GUI, do a restart, let it finish and then
mail me the collection of /var/opt/SUNWut/tmp/admincgi-truss.*
files. They're probably going to be a bit too big to post to the
mailing list.
Obviously to revert to the original CGI just:
mv admincgi-bin admincgi
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
