Sponsored Content
Top Forums UNIX for Advanced & Expert Users error messages in /var/adm/messages Post 302114618 by sysgate on Tuesday 17th of April 2007 10:17:33 AM
Old 04-17-2007
I spent some time googling for those errors, honestly, didn't find anything related, better call sun support.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

error in /var/adm/messages

I have an error in my /var/adm/messages that states: (*hostname*) inetd : fs/tcp: bind: Address already in use. It repeats it self over and over. I have looked everywhere I can think of on the net but cant find anything. HELP Please:confused: (2 Replies)
Discussion started by: julie
2 Replies

2. Solaris

[urgent help] error log on /var/adm/messages

hi experts, i'm having more error log on /var/adm/messages could anyone help to description what is this error logs means???? and how to fix it? below is the logs : Nov 22 20:03:40 USSDGtbs-1 unix: Nov 22 20:03:40 USSDGtbs-1 ^Mpanic/thread=3001345edc0: Nov 22 20:03:40 USSDGtbs-1 unix: ... (2 Replies)
Discussion started by: bucci
2 Replies

3. Solaris

/var/adm/messages error

I am frequently getting following errors in /var/adm/messages. I am using solaris 8 Nov 7 16:03:03 Server Name SRS Proxy: unhandled exception: compareTimestamps format() Nov 7 16:06:57 servername sendmail: lA2MadB5007315: to=postmaster, delay=4+22:30:07, xdelay=00:00:00, mailer=relay,... (2 Replies)
Discussion started by: sunsri01
2 Replies

4. Solaris

Info req: /var/adm/messages - Kern.warning - different ID messages

Hi all, where I can find a list and meaning of the ID number (for example ID 353554 kern.warning)? Thanks in advance Pierluigi (1 Reply)
Discussion started by: Petrucci
1 Replies

5. Solaris

Error messages in /var/adm

Hi, I get this messages in my /var/adm/messages can you please tell me the reason for recieving this kind of messages and how to debug? Admin 2418029 Error: Host port combo with host . Unable to resolve name Tools 2206121 Error: ERROR.. gethostbyname() failed for errno Admin... (3 Replies)
Discussion started by: lbreddy
3 Replies

6. Solaris

Error in /var/adm/messages

Hi All, I m new to Solaris environment, Right now I m using Solaris 10. I get continuously following waring message in `messages` file so var partition going to full. plz help me to stop these messages. Feb 8 15:58:47 TSAS px: WARNING: px1: spurious interrupt from ino... (2 Replies)
Discussion started by: vikas898
2 Replies

7. Solaris

Getting continually error message in /var/adm/messages.

Hi Friends, Please help me to resove this issue ASAP. Nov 17 16:25:52 server1 sendmail: pAH8Pnh22099: SYSERR: putoutmsg (NO-HOST): error on output channel sending "553 5.1.3 @123.com.... User address required": File too large Nov 17 16:25:53 server1 sendmail: pAH8Pnh22099:... (1 Reply)
Discussion started by: holds_me
1 Replies

8. Emergency UNIX and Linux Support

Error filling /var/adm/messages

I have Solaris-11 non-global zone running under Solaris-11 global zone. Every few minutes, this message is getting in /var/adm/message of non-global zone Aug 31 08:31:53 zonnjc002dbp01 statd: statd: cannot talk to statd at NAS1, RPC: Timed out(5) NAS1 is already mounted as NFS and working... (2 Replies)
Discussion started by: solaris_1977
2 Replies

9. Solaris

Login error in /var/adm/messages

I had an issue with ssh on one of my servers and noticed the following errors, listed below. Errors in /var/adm/messagessshd lastlog_perform_login: Couln't stat /var/adm/lastlog: permission denied sshd lastlog_openseek: /var/adm/lastlog is not a file or directory! automountd self_check:... (0 Replies)
Discussion started by: bitlord
0 Replies

10. Solaris

Local zone is not logging systems messages to /var/adm/messages

This is isolated to just 1 non-global zone out of many zones managed This is a Solaris 11 system on SPARC This is NOT a branded zone syslogd is active This came to our attention when one of our scripts didn't run over the weekend prompting us to check our messages logging in... (6 Replies)
Discussion started by: samthewildone
6 Replies
RESTART_SYSCALL(2)					     Linux Programmer's Manual						RESTART_SYSCALL(2)

NAME
restart_syscall - restart a system call after interruption by a stop signal SYNOPSIS
int restart_syscall(void); Note: There is no glibc wrapper for this system call; see NOTES. DESCRIPTION
The restart_syscall() system call is used to restart certain system calls after a process that was stopped by a signal (e.g., SIGSTOP or SIGTSTP) is later resumed after receiving a SIGCONT signal. This system call is designed only for internal use by the kernel. restart_syscall() is used for restarting only those system calls that, when restarted, should adjust their time-related parameters--namely poll(2) (since Linux 2.6.24), nanosleep(2) (since Linux 2.6), clock_nanosleep(2) (since Linux 2.6), and futex(2), when employed with the FUTEX_WAIT (since Linux 2.6.22) and FUTEX_WAIT_BITSET (since Linux 2.6.31) operations. restart_syscall() restarts the interrupted system call with a time argument that is suitably adjusted to account for the time that has already elapsed (including the time where the process was stopped by a signal). Without the restart_syscall() mechanism, restarting these system calls would not correctly deduct the already elapsed time when the process continued execution. RETURN VALUE
The return value of restart_syscall() is the return value of whatever system call is being restarted. ERRORS
errno is set as per the errors for whatever system call is being restarted by restart_syscall(). VERSIONS
The restart_syscall() system call is present since Linux 2.6. CONFORMING TO
This system call is Linux-specific. NOTES
There is no glibc wrapper for this system call, because it is intended for use only by the kernel and should never be called by applica- tions. The kernel uses restart_syscall() to ensure that when a system call is restarted after a process has been stopped by a signal and then resumed by SIGCONT, then the time that the process spent in the stopped state is counted against the timeout interval specified in the original system call. In the case of system calls that take a timeout argument and automatically restart after a stop signal plus SIGCONT, but which do not have the restart_syscall(2) mechanism built in, then, after the process resumes execution, the time that the process spent in the stop state is not counted against the timeout value. Notable examples of system calls that suffer this problem are ppoll(2), select(2), and pselect(2). From user space, the operation of restart_syscall() is largely invisible: to the process that made the system call that is restarted, it appears as though that system call executed and returned in the usual fashion. SEE ALSO
sigaction(2), sigreturn(2), signal(7) Linux 2014-12-31 RESTART_SYSCALL(2)
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy