Sponsored Content
Operating Systems Linux Red Hat Process with S state(Interruptable) in RHEL and gives Advertise error after restarting/Killing the p Post 303006520 by Rohits on Friday 3rd of November 2017 05:32:02 AM
Old 11-03-2017
Quote:
Originally Posted by hicksd8
"Advertise Error" is a RFS (Receive Flow Steering) specific error but am I right in saying that you only get this error when you kill the process and then try to restart it. The problem is probably that the new process is trying to advertise a resource still advertised by the killed process.

The question is why the uninterruptable S state process is worrying you in the first place. What is happening that prompts you to mess with it? Why don't you just leave it alone?

Reference: Search for "Linux error 68 EADV"
Yes you got it right, every time I am starting the Process it is giving me "Advertise Error", and the process is not behaving the way it supposed to, until the reboot of Server.
So I had to check the state of the process and I got this. Living with it is kind of difficult.
So can you please tell me how to get rid of the advertise error.

Thanks

Last edited by Rohits; 11-03-2017 at 07:14 AM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Restarting a Crashed Process

Hello, I host a couple of Call of Duty gameing servers. There are some hackers who love the crash them. When they crash them it simply causes a segmentaion fault and kills the PID. I was wondering it you could help me write a script to simply restart the program after it has been crashed. The... (9 Replies)
Discussion started by: Phobos
9 Replies

2. Shell Programming and Scripting

Killing of a process and send a mail if the process doesnot come up within 2 minutes

Hi Friends, I am new to this forum as well as new to shell scripting. I have a problem here and i need someone to solve this. Let us consider there are two processes(abc & def).There is a script which kills these two processes(i.e killtheprocess abc). Here abc is the argument . There is a... (1 Reply)
Discussion started by: Prince89
1 Replies

3. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

4. UNIX and Linux Applications

Unix pkill error; does wily obstruct me killing the process?

have two scripts on Unix; one that starts some processes and the other one for killing a process. At first, I ran the .sh without WILY in it and it worked perfectly; in this way, I could also ran my stopper process. However I need WILY in this so I added it to my script but this time, a message... (1 Reply)
Discussion started by: nerdogan551
1 Replies

5. UNIX for Dummies Questions & Answers

Restarting a process

Hi, How is it possible to restart only your process. I can get the process killed but I am not able to start it. For eg : i first did this ps -ef|grep _out --displays all the process with _out in the name then I killed kill -15 36044 -- process id. Now how can i start the same... (1 Reply)
Discussion started by: TH3M0Nk
1 Replies

6. Solaris

SSH : Restarting too quickly, changing state to maintenance

Hi, I'm new to Solaris. I have an issue with ssh service. When I restart the service it exits with an exit status of 0 $svcadm restart svc:/network/ssh:default $echo $? 0 $ However, the service goes into maintenance mode after restart. I'm able to connect even though the service is in... (3 Replies)
Discussion started by: maverick_here
3 Replies

7. Shell Programming and Scripting

Need help in restarting process

Hi friends, I have one unix command which is used to check the network status manually. followig is the command check_Network this command give follwoing status Network 1 is ok Network 2 is ok network 3 is ok network 4 is ok . . . . Network 10 is... (8 Replies)
Discussion started by: Nakul_sh
8 Replies

8. BSD

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies

9. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies

10. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
strace(8)						      System Manager's Manual							 strace(8)

NAME
strace - Writes STREAMS event trace messages to standard output SYNOPSIS
/usr/sbin/strace [mod_ID sub_ID pri_level] DESCRIPTION
The strace command gets STREAMS event trace messages from STREAMS drivers and modules via the STREAMS log driver (strlog), and writes these messages to standard output. You can limit the messages strace receives by specifying arguments to the command. The arguments, which must be specified together, are the following: Specifies the STREAMS module identification number. Specifies a subidentification number (often corresponding to a minor device). Specifies a tracing priority level. The strace command will get messages of a level equal to or less than the value in the pri_level argument. The value of the argument must be a nonnegative integer. You can specify all as the value for any of the arguments in the strace command line. The value all indicates that there are no restric- tions for that argument. You can also specify multiple sets of the command's three arguments to obtain the messages from more than one driver or module. More than one strace process can open the STREAMS log driver at a time. When you invoke strace, the log driver compares the sets of argu- ments from the command line with actual trace messages, returning the messages that satisfy the criteria. STREAMS event trace messages have the following format: seqnum stdtime tickstime pri_level ntfycode mod_ID sub_ID msgtext where: The event trace sequence number. The time the message was sent, in the format hh:mm:ss. The time the message was sent, measured in machine ticks since the last boot. The tracing priority level as defined by the STREAMS driver or module that originates the messages. Can be either of the following indicators: Indicates that the message has also been saved in the error log. Indicates that the message signaled a fatal error. The module identification number of the trace message source. The subidentification number of the trace message source. The trace message text. The strace command runs until terminated by the user. NOTES
Running strace with several sets of arguments can negatively affect STREAMS performance, particularly for those modules and drivers sending the messages. Also be aware that strace may not be able to handle a large number of messages. If drivers and modules return messages to strace too quickly, some may be lost. EXAMPLES
To display all trace messages received from the driver or module identified by mod_ID 28, enter: strace 28 all all To display those trace messages from the driver or module identified by mod_ID 28 and its minor devices identified by the sub_IDs 2, 3, and 4, enter: strace 28 2 all 28 3 all 28 4 all This command line causes messages of any tracing priority level to be displayed. To display the trace messages from the same driver or module and sub_IDs, but limited to certain priority levels, enter: strace 28 2 0 28 3 0 28 4 1 This command line specifies that messages from driver or module 28 and sub_IDs 2 and 3 must have a tracing priority of 0, and those from sub_ID 4 must have a tracing priority equal to or less than 1. RELATED INFORMATION
Commands: strclean(8), strerr(8). Interfaces: strlog(7). delim off strace(8)
All times are GMT -4. The time now is 02:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy