dbTalk Databases Forums  

XP server not running (UNIX solaris, ASE 12.5)

comp.databases.sybase comp.databases.sybase


Discuss XP server not running (UNIX solaris, ASE 12.5) in the comp.databases.sybase forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Kathie Beshoner
 
Posts: n/a

Default XP server not running (UNIX solaris, ASE 12.5) - 05-25-2004 , 01:59 PM






Last week when the XP server was not running, I issued the isql
command xp_cmdshell "who" to get the XP server started and this worked
fine.
Yesterday, when I tried this, the command hung for a while and then
the isql prompt returned. The server log became extremely full with
messages about aiowait. I removed the large file yesterday. Today
the system complains that the file system is full, but there is not
any large files there anymore.
Help. Please.

Reply With Quote
  #2  
Old   
Mark A. Parsons
 
Posts: n/a

Default Re: XP server not running (UNIX solaris, ASE 12.5) - 05-25-2004 , 02:30 PM






Kathie Beshoner wrote:
Quote:
Last week when the XP server was not running, I issued the isql
command xp_cmdshell "who" to get the XP server started and this worked
fine.
Yesterday, when I tried this, the command hung for a while and then
the isql prompt returned. The server log became extremely full with
messages about aiowait. I removed the large file yesterday. Today
the system complains that the file system is full, but there is not
any large files there anymore.
Help. Please.
Run 'df' to get a listing of all file systems on your box ... look for any
file systems that are full and see if any of those correspond to any
directories in use by Sybase (XP, ASE, BackupServer, etc.) ... then see if
you can track down the culprit. It may not be you but some other user
filling up a file system that you (XP?) need access to.

If you can't track down the culprit, ask your sysadmin to help out with
locating the bad guy so and freeing up some space on said file system.

--
Mark A. Parsons

Iron Horse, Inc.
iron_horse (AT) NOSPAM (DOT) compuserve.com


Reply With Quote
  #3  
Old   
Sara Law
 
Posts: n/a

Default Re: XP server not running (UNIX solaris, ASE 12.5) - 05-25-2004 , 07:14 PM



kbeshoner (AT) dot (DOT) state.az.us (Kathie Beshoner) wrote in message news:<bba55780.0405251059.6f373ead (AT) posting (DOT) google.com>...
Quote:
Last week when the XP server was not running, I issued the isql
command xp_cmdshell "who" to get the XP server started and this worked
fine.
Yesterday, when I tried this, the command hung for a while and then
the isql prompt returned. The server log became extremely full with
messages about aiowait. I removed the large file yesterday. Today
the system complains that the file system is full, but there is not
any large files there anymore.
Help. Please.
Hi Kathie ...

You MAY have to actually bring the server down, issue another "rm"
command, and then bring it back up; or perhaps just re-booting it will
suffice. Just a thought. What was the detail of the "aiowait"
message? Are you running (I hope!) with asynchronous I/O to your
devices?? Sorry I have not experienced this problem directly, so have
no first-hand experience.

Also, I am in Phoenix ... are you as well? If you would like to
correspond more directly, let me know!!

Sara Law (American Express) ...


Reply With Quote
  #4  
Old   
Michael Peppler
 
Posts: n/a

Default Re: XP server not running (UNIX solaris, ASE 12.5) - 05-26-2004 , 01:03 AM



On Tue, 25 May 2004 11:59:28 -0700, Kathie Beshoner wrote:

Quote:
Last week when the XP server was not running, I issued the isql command
xp_cmdshell "who" to get the XP server started and this worked fine.
Yesterday, when I tried this, the command hung for a while and then the
isql prompt returned. The server log became extremely full with messages
about aiowait. I removed the large file yesterday. Today the system
complains that the file system is full, but there is not any large files
there anymore.
If you "rm" a file that is currently open then the file will *appear* to
be removed, but the data will still be there.

One way that I have used to truncate an ASE log file without restarting
ASE is to cp /dev/null to the logfile, for example:

cp FOO.log FOO.log.save
cp /dev/null FOO.log

You will/may lose a few log messages this way (between the first and
second cp).

Michael
--
Michael Peppler Data Migrations, Inc.
mpeppler (AT) peppler (DOT) org http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.peppler.org/resume.html



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.