Re: "Got notification..." message
On Sat, 26 Jan 2019, Cindy-Sue Causey wrote: On 1/26/19, Pierre Frenkiel wrote: hi, I just discovred today that I have every day, in syslog, more than 10 lines of message like: inetd.service: Got notification message from PID 31376, but reception only permitted for main PID 10222 (I didn't find any useful answer from Google) I'm not aware of any not working program, but it's rather frustating, in addition that syslog is unusually very big, every day. This is coming from someone who was naive about this a half hour ago. I knew UUID and UID were about identification so I searched "what is pid identification linux". Landed information that it's about "process identification"... so I gave "ps aux" a shot by letting it run wide open. I wanted to see if "ps" labels the columns. It does. Second column = PID. The numbers there change CONSTANTLY depending on how we open and close everything we do. That's another of those Life lessons learned on the fly because things like PysolFC, Firefox, and Xfce4-terminal all change for me constantly during each session. You always have to track down that new number during those times you might have to do things like... "kill". :D The reason I'm saying that is because something else likely now bears the numbers you shared. It's further no shock that you couldn't find an exact match online because that is VERY specific to your usage. If you reboot after reading this. something else yet again possibly will be represented by those same two figures *IF* they even appear at all. So... maybe see if you can identify which two processes go by whatever numbers appear for the newest lines to see if those packages are still running. You *possibly* can do that very quickly by placing your newest numbers where I used "1136" in my example for terminal command "ps aux | grep 1136": $ ps aux | grep 1136 candyca+ 1136 0.0 0.4 297668 4684 ?Sl Jan24 2:13 /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray candyca+ 25753 0.0 0.0 6384 796 pts/1S+ 15:13 0:00 grep 1136 Maybe, anyway. This is totally by the seat of my britches because no one else had had a chance to answer yet. I'm bold in posting it because it's actually working in a comprehensible way with my setup here just this second. :) That "reception only permitted for main" that you're seeing tells me something's trying to share a message, sometimes simply an advisement but also possibly a warning or error, in a way that it's not allowed to do, but I'm not sure how *to attempt* to work through that without knowing exactly what's involved. My still naive reading of what you're seeing is that "PID 31376" is trying to communicate with, hopefully just advise "inetd.service", but whatever "PID 31376" is sending is only permitted to be used/accessed by "PID 10222". thank you for your long answer, but alas it explains nothing... I don't know why I had 4 inetd running processes, and why some tried to communicate with an other one. today, I only have 1 best regards, -- Pierre Frenkiel
Re: "Got notification..." message
On Sat, Jan 26, 2019 at 03:32:24PM -0500, Cindy-Sue Causey wrote: > This is coming from someone who was naive about this a half hour ago. > I knew UUID and UID were about identification so I searched "what is > pid identification linux". To clarify: "UID" is User IDentifier. It's a number that your login name maps to (usually 1000 or so on Debian), and is how the system keeps track of user accounts. Human-readable names like "greg" or "cindy" are only for humans. What really matters is the UID number. "UUID" is Universally Unique IDentifier. It's a string of digits and dashes that a computer is supposed to be able to generate in such a way that another computer (or a different process on the same computer) will not create the same one. It's kind of like a random number, except with the intent that nobody else can get the same number. https://en.wikipedia.org/wiki/Universally_unique_identifier UUIDs have nothing to do with the identification of people. A UUID is generated when you create a new file system on a disk partition. This UUID is (supposedly) unique to that file system, and allows the system to know which file system is which, so it can mount them all in the correct places. Even if the device changes from /dev/sdb to /dev/sdc or whatever. Other uses exist, but that's the one that people are most likely to encounter.
Re: "Got notification..." message
Cindy-Sue Causey wrote: ... > As an aside, I sent "ps aux" to a text file to easily view that first > column. The file's only 165 lines long yet the PID column's last > sequentially numbered entry at that second was "28909". That makes me > curious as to how those are assigned. Were there that many processes > that opened then closed when finished, or are there classes of PIDs > that things fall into, or. :) PIDs are assigned when a new process is started, the range is between 0 and 32K with 0 and 1 being used by systemd or whatever init you are using. top is an interesting command to use along with ps. songbird
Re: "Got notification..." message
On 1/26/19, Cindy-Sue Causey wrote: > On 1/26/19, Pierre Frenkiel wrote: >> hi, >> I just discovred today that I have every day, in syslog, more than 10 >> lines of message like: >> >> inetd.service: Got notification message from PID 31376, but reception >> only permitted for main PID 10222 >> >> (I didn't find any useful answer from Google) >> I'm not aware of any not working program, but it's rather frustating, in >> addition that syslog is unusually very big, every day. > > < some rambling of my own snipped > > > So... maybe see if you can identify which two processes go by whatever > numbers appear for the newest lines to see if those packages are still > running. You *possibly* can do that very quickly by placing your > newest numbers where I used "1136" in my example for terminal command > "ps aux | grep 1136": > > $ ps aux | grep 1136 > candyca+ 1136 0.0 0.4 297668 4684 ?Sl Jan24 2:13 > /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray > candyca+ 25753 0.0 0.0 6384 796 pts/1S+ 15:13 0:00 grep 1136 I had never tracked down what "ps" is. It's a snapshot of running processes. Process snapshot. ps. Found this in "man ps" $ ps -q 1136 -o comm= MUCH NICER. It presents this instead of all that excess feedback from "ps aux": $ ps -q 1136 -o comm= wicd-client MUCH NICER. Much cleaner, much easier to grasp that particular information when needed. < whole bunch more of my own rambling snipped > Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: "Got notification..." message
On 1/26/19, Pierre Frenkiel wrote: > hi, > I just discovred today that I have every day, in syslog, more than 10 > lines of message like: > > inetd.service: Got notification message from PID 31376, but reception > only permitted for main PID 10222 > > (I didn't find any useful answer from Google) > I'm not aware of any not working program, but it's rather frustating, in > addition that syslog is unusually very big, every day. This is coming from someone who was naive about this a half hour ago. I knew UUID and UID were about identification so I searched "what is pid identification linux". Landed information that it's about "process identification"... so I gave "ps aux" a shot by letting it run wide open. I wanted to see if "ps" labels the columns. It does. Second column = PID. The numbers there change CONSTANTLY depending on how we open and close everything we do. That's another of those Life lessons learned on the fly because things like PysolFC, Firefox, and Xfce4-terminal all change for me constantly during each session. You always have to track down that new number during those times you might have to do things like... "kill". :D The reason I'm saying that is because something else likely now bears the numbers you shared. It's further no shock that you couldn't find an exact match online because that is VERY specific to your usage. If you reboot after reading this. something else yet again possibly will be represented by those same two figures *IF* they even appear at all. So... maybe see if you can identify which two processes go by whatever numbers appear for the newest lines to see if those packages are still running. You *possibly* can do that very quickly by placing your newest numbers where I used "1136" in my example for terminal command "ps aux | grep 1136": $ ps aux | grep 1136 candyca+ 1136 0.0 0.4 297668 4684 ?Sl Jan24 2:13 /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray candyca+ 25753 0.0 0.0 6384 796 pts/1S+ 15:13 0:00 grep 1136 Maybe, anyway. This is totally by the seat of my britches because no one else had had a chance to answer yet. I'm bold in posting it because it's actually working in a comprehensible way with my setup here just this second. :) That "reception only permitted for main" that you're seeing tells me something's trying to share a message, sometimes simply an advisement but also possibly a warning or error, in a way that it's not allowed to do, but I'm not sure how *to attempt* to work through that without knowing exactly what's involved. My still naive reading of what you're seeing is that "PID 31376" is trying to communicate with, hopefully just advise "inetd.service", but whatever "PID 31376" is sending is only permitted to be used/accessed by "PID 10222". OR NOT, but that would be my first a-sumption if this had been found on my machine. :) As an aside, I sent "ps aux" to a text file to easily view that first column. The file's only 165 lines long yet the PID column's last sequentially numbered entry at that second was "28909". That makes me curious as to how those are assigned. Were there that many processes that opened then closed when finished, or are there classes of PIDs that things fall into, or. :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
"Got notification..." message
hi, I just discovred today that I have every day, in syslog, more than 10 lines of message like: inetd.service: Got notification message from PID 31376, but reception only permitted for main PID 10222 (I didn't find any useful answer from Google) I'm not aware of any not working program, but it's rather frustating, in addition that syslog is unusually very big, every day. best regards, -- Pierre Frenkiel
