View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 43 posts ] 
Go to page Previous  1, 2, 3  Next

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 5:09 pm 
Offline
Joined: Wed Jan 04, 2006 10:20 am
Posts: 366
Location: South New Jersey, USA
Is there a legacy driver that we could try?

_________________
LINHES 8.3 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 1GB Ram. 1.5TB WD. HDHR Prime & PVR150. Nvidia GT210. Silver remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 5:27 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1095
Location: SC
340xx is already legacy. Maybe the 304xx:
Code:
VGACARDTYPE="nvidia-304xx" xconfig.sh


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 6:00 pm 
Offline
Joined: Wed Jan 04, 2006 10:20 am
Posts: 366
Location: South New Jersey, USA
The 304 xconfig went through with no problem but after a reboot, the end result is the same. Stalled at the splash screen.

_________________
LINHES 8.3 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 1GB Ram. 1.5TB WD. HDHR Prime & PVR150. Nvidia GT210. Silver remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 7:44 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
I tried the 304 install, it installed without problem but the boot splash neither continued during the next X start, nor did it work after a reboot. Same thing with the splash.

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 8:53 pm 
Offline
Joined: Wed Jan 04, 2006 10:20 am
Posts: 366
Location: South New Jersey, USA
Vesa works for me but no sound. Maybe unrelated.

_________________
LINHES 8.3 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 1GB Ram. 1.5TB WD. HDHR Prime & PVR150. Nvidia GT210. Silver remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 9:49 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
I set it to VESA to make sure I could get in and wanted to at least make sure my database etc upgraded while we continue investigating the GPU driver issue.

However, I'm not sure what this means:

"Run mythtv-setup (or Alt+S) and update the Myth database."

I am in mythtv-setup but it isn't clear where/what is required to "update the Myth database" can anyone elaborate?

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sat Dec 09, 2017 10:13 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
I'm also having the issue where mythtv-setup can't connect to the backend database.

I've been using this for about 9 years so I'm afraid some of my settings are lost to ancient memory. I vaguely recall using an explicit IP in the past, so I edited the config.xml and put the IP of the machine rather than 127.0.0.1 but it still isn't working. Is there a way to get mythbackend to tell me what it is listening on? The machine only has one interface (wired ethernet).

-Jeff


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 1:37 pm 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 913
Location: Lexington, Ky
Jeff,
As I recall once your in setup you should get a splash screen that asks if you want to upgrade the database.


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 2:30 pm 
Offline
Joined: Wed Jan 07, 2004 12:14 pm
Posts: 392
Location: Charlotte, NC
Well I can confirm that 1) the splash screen for schema update doesn't seem to be in this version and 2) just entering mythtv-setup and doing something (anything) does update the schema (all my frontends see the changed DB but nothing can connect)...

_________________
Backend server - 3.75 TB 3.0ghz dual core 6 gig RAM, nVidia 9400, Gigabyte GA-870A-UD3 MB, 2 HD-5500, 2 HD Homerun dual tuners, 3 frontend machines - LinHES 8.5


Top
 Profile  
 
PostPosted: Sun Dec 10, 2017 3:10 pm 
Offline
Joined: Wed Dec 28, 2005 8:43 am
Posts: 8
Location: San Antonio
I updated an existing atom based Nvidia Ion server and another client on similar hardware that I have been using for years.
Yes, an old ION GPU atom board is serving very very good as a backend/frontend with Hidef recordings and media library.

I however had a very frustrating morning through the afternoon due to my own ignorance.

My issues boiled down to the following:
* Database could not start. "Cannot Connect to Backend"
* Could not connect to back-end once started
* Clients could not find the server.
* Could not record or watch live TV.

Solutions in order that I solved them:

* Manually started the database.
* Entered the setup on the backend and manually entered the IP address of the backend's IP.
* Manually had to tick something on the backend to the effect of saying "This is the main backend"
* I had to manually chown & chmod mythtv as the owner of the recording /data/storage directories.

Then like the super cool magic that is LinHES, everything worked.

One side note: in an act of desperation I was about to reinstall linHES on the thin client. This Nvidia ION gpu based atom processor failed on starting the installer for 8.5. Trying no splash did not work.

Anyhow, the upgrade seemed to change a few things that need to be reset. Once done, everything should work.

Rip

_________________
Man, I thought I was confused but I've learned enough to see that I really have no clue.


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 4:23 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1095
Location: SC
For those of you on the Nvidia 340 driver that are having problems please try this and report back:
Code:
sudo pacman -U http://linhes.org/repo/x86_64/core-testing/nvidia-340xx-340.104-8-x86_64.pkg.tar.xz


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 4:41 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1095
Location: SC
nbdwt73,

The schema update screen in mythtv-setup does come up if the DB hasn't already been updated. I just confirmed it on a test system that was on 0.28. My guess is that when you rebooted mythbackend started before you ran mythtv-setup and it updated the DB. Check the mythbackend logs. You can also use find_orphans.py to see where the backup file for the DB update is located.

As for not connecting did you go into mythtv-setup > General > Host Address Backend Setup and confirm the IPs and Save the changes. As with Big Boy Stan I am thinking some of the new myth 29 networking settings are not updated in your DB.


Top
 Profile  
 
PostPosted: Sun Dec 10, 2017 4:45 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1095
Location: SC
ripley wrote:
* Manually started the database.
Are you referring to mysql here or just mythbackend?

ripley wrote:
* I had to manually chown & chmod mythtv as the owner of the recording /data/storage directories.
What was the owner of these before chown?


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 7:53 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
brfransen wrote:
For those of you on the Nvidia 340 driver that are having problems please try this and report back:
Code:
sudo pacman -U http://linhes.org/repo/x86_64/core-testing/nvidia-340xx-340.104-8-x86_64.pkg.tar.xz


I just tried this, and while I can't be 100% certain yet, it appears to have worked for the video driver.

I will get in to the logs now and confirm it loaded with the NVidia driver and didn't use the previous VESA setting I did by hand, and I will report back.

Still having the mythbackend problem. The explicit IP is set and the "this host is the mythbackend" or similar option is also checked in MythSetup but it keeps looping and won't let me navigate around the setup menus to see what is broken due to not being able to connect to the backend.

More shortly. A big thank you to brfransen for his help.

-Jeff

** UPDATE **

Looks like the NVidia change worked and that is my current driver (I am in the setup menu now after a normal boot, post install):

From
[root@mythtv log]# tail -400 Xorg.0.log

[ 27.355] (II) VESA(0): initializing int10
[ 27.355] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 27.409] (II) VESA(0): VESA BIOS detected
[ 27.409] (II) VESA(0): VbeVersion is 768, OemStringPtr is 0x00002100,
OemVendorNamePtr is 0x00002107, OemProductNamePtr is 0x0000211a,
OemProductRevPtr is 0x00002131
[ 27.409] (II) VESA(0): VESA VBE Version 3.0
[ 27.409] (II) VESA(0): VESA VBE Total Mem: 14336 kB
[ 27.409] (II) VESA(0): VESA VBE OEM: NVIDIA
[ 27.409] (II) VESA(0): VESA VBE OEM Software Rev: 98.121
[ 27.409] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[ 27.409] (II) VESA(0): VESA VBE OEM Product: MCP79 Board - mcp7a-uo
[ 27.409] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
[ 27.409] (II) VESA(0): virtual address = 0x7f9cd27d2000,
physical address = 0xd1000000, size = 14680064
[ 27.416] (II) VESA(0): Setting up VESA Mode 0x17B (1280x720)
[ 27.609] (==) VESA(0): Default visual is TrueColor


Top
 Profile  
 
 Post subject: Re: Upgrade 8.4 to 8.5
PostPosted: Sun Dec 10, 2017 8:03 pm 
Offline
Joined: Fri Mar 26, 2004 9:00 am
Posts: 239
In the "MythTV Startup Status" window (on screen now) I have

"Unable to connect to master backend.

Selection an option below:

[progress bar to 100%]

And the Retry/Search/Setup/Exit buttons"

If I exit it loops back in to here, search doesn't turn up anything and a retry times out. Setup confirms the settings show in config.xml below which is the IP of the machine.

[root@mythtv 2017-12-10]# tail -100 mythtv_mythbackend.log

2017-12-10T17:57:50.866001-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7981 (reconnectTimeout) MainServer: Connecting to master server: 192.168.2.141:6543
2017-12-10T17:57:50.866105-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7992 (reconnectTimeout) MainServer: Connected successfully
2017-12-10T17:58:20.886185-08:00 mythbackend[2483]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(5637b923a7e0:53): ReadStringList: Error, timed out after 30000 ms.
2017-12-10T17:58:20.886356-08:00 mythbackend[2483]: W MythSocketThread(-1) mainserver.cpp:7694 (connectionClosed) MainServer: Unknown socket closing MythSocket(0x5637b923a7e0)
2017-12-10T17:58:20.886516-08:00 mythbackend[2483]: E CoreContext mythsocket.cpp:369 (SendReceiveStringList) MythSocket(5637b923a7e0:-1): No response.
2017-12-10T17:58:20.886641-08:00 mythbackend[2483]: E CoreContext mainserver.cpp:8030 (reconnectTimeout) MainServer: Failed to open master server socket, timeout
2017-12-10T17:58:20.886887-08:00 mythbackend[2483]: I MythSocketThread(53) mainserver.cpp:7683 (connectionClosed) Control sock(5637b92390d0) disconnected
2017-12-10T17:58:20.887063-08:00 mythbackend[2483]: I MythSocketThread(60) mainserver.cpp:7683 (connectionClosed) Control sock(5637b9216380) disconnected
2017-12-10T17:58:20.887258-08:00 mythbackend[2483]: I MythSocketThread(57) mainserver.cpp:7683 (connectionClosed) Control sock(5637b8fbb280) disconnected
2017-12-10T17:58:20.887427-08:00 mythbackend[2483]: E MythSocketThread(57) mythsocket.cpp:722 (WriteStringListReal) MythSocket(5637b8fbb280:-1): WriteStringList: Error, called with unconnected socket.
2017-12-10T17:58:20.887621-08:00 mythbackend[2483]: I ProcessRequest mainserver.cpp:1738 (HandleAnnounce) MainServer: MainServer::ANN Frontend
2017-12-10T17:58:20.887749-08:00 mythbackend[2483]: I ProcessRequest mainserver.cpp:1743 (HandleAnnounce) MainServer: adding: mythtv.local(5637b922f640) as a client (events: 0)
2017-12-10T17:58:20.888020-08:00 mythbackend[2483]: I ProcessRequest mainserver.cpp:1738 (HandleAnnounce) MainServer: MainServer::ANN Monitor
2017-12-10T17:58:20.888170-08:00 mythbackend[2483]: I ProcessRequest mainserver.cpp:1743 (HandleAnnounce) MainServer: adding: mythtv.local(5637b8fbb280) as a client (events: 1)
2017-12-10T17:58:21.789047-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7981 (reconnectTimeout) MainServer: Connecting to master server: 192.168.2.141:6543
2017-12-10T17:58:21.789153-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7992 (reconnectTimeout) MainServer: Connected successfully
2017-12-10T17:58:46.006087-08:00 mythbackend[2483]: I MythSocketThread(64) mainserver.cpp:7643 (connectionClosed) Playback sock(5637b922f640) 'mythtv.local' disconnected
2017-12-10T17:58:46.006220-08:00 mythbackend[2483]: I MythSocketThread(51) mainserver.cpp:7643 (connectionClosed) Monitor sock(5637b8fbb280) 'mythtv.local' disconnected
2017-12-10T17:58:51.809994-08:00 mythbackend[2483]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(5637b923a7e0:55): ReadStringList: Error, timed out after 30000 ms.
2017-12-10T17:58:51.810098-08:00 mythbackend[2483]: W MythSocketThread(-1) mainserver.cpp:7694 (connectionClosed) MainServer: Unknown socket closing MythSocket(0x5637b923a7e0)
2017-12-10T17:58:51.810193-08:00 mythbackend[2483]: E CoreContext mythsocket.cpp:369 (SendReceiveStringList) MythSocket(5637b923a7e0:-1): No response.
2017-12-10T17:58:51.810286-08:00 mythbackend[2483]: E CoreContext mainserver.cpp:8030 (reconnectTimeout) MainServer: Failed to open master server socket, timeout
2017-12-10T17:58:51.810608-08:00 mythbackend[2483]: I MythSocketThread(51) mainserver.cpp:7683 (connectionClosed) Control sock(5637b9248580) disconnected
2017-12-10T17:58:52.811307-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7981 (reconnectTimeout) MainServer: Connecting to master server: 192.168.2.141:6543
2017-12-10T17:58:52.811412-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7992 (reconnectTimeout) MainServer: Connected successfully
2017-12-10T17:59:22.839248-08:00 mythbackend[2483]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(5637b8fc31a0:54): ReadStringList: Error, timed out after 30000 ms.
2017-12-10T17:59:22.839309-08:00 mythbackend[2483]: W MythSocketThread(-1) mainserver.cpp:7694 (connectionClosed) MainServer: Unknown socket closing MythSocket(0x5637b8fc31a0)
2017-12-10T17:59:22.839384-08:00 mythbackend[2483]: E CoreContext mythsocket.cpp:369 (SendReceiveStringList) MythSocket(5637b8fc31a0:-1): No response.
2017-12-10T17:59:22.839454-08:00 mythbackend[2483]: E CoreContext mainserver.cpp:8030 (reconnectTimeout) MainServer: Failed to open master server socket, timeout
2017-12-10T17:59:22.839510-08:00 mythbackend[2483]: I MythSocketThread(54) mainserver.cpp:7683 (connectionClosed) Control sock(5637b92204d0) disconnected
2017-12-10T17:59:22.839565-08:00 mythbackend[2483]: I ProcessRequest mainserver.cpp:1738 (HandleAnnounce) MainServer: MainServer::ANN Monitor
2017-12-10T17:59:22.839619-08:00 mythbackend[2483]: I ProcessRequest mainserver.cpp:1743 (HandleAnnounce) MainServer: adding: mythtv.local(5637b920e740) as a client (events: 0)
2017-12-10T17:59:23.440984-08:00 mythbackend[2483]: I MythSocketThread(55) mainserver.cpp:7643 (connectionClosed) Monitor sock(5637b920e740) 'mythtv.local' disconnected
2017-12-10T17:59:23.841441-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7981 (reconnectTimeout) MainServer: Connecting to master server: 192.168.2.141:6543
2017-12-10T17:59:23.841546-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7992 (reconnectTimeout) MainServer: Connected successfully
2017-12-10T17:59:53.860855-08:00 mythbackend[2483]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(5637b920b600:60): ReadStringList: Error, timed out after 30000 ms.
2017-12-10T17:59:53.860960-08:00 mythbackend[2483]: W MythSocketThread(-1) mainserver.cpp:7694 (connectionClosed) MainServer: Unknown socket closing MythSocket(0x5637b920b600)
2017-12-10T17:59:53.861055-08:00 mythbackend[2483]: E CoreContext mythsocket.cpp:369 (SendReceiveStringList) MythSocket(5637b920b600:-1): No response.
2017-12-10T17:59:53.861148-08:00 mythbackend[2483]: E CoreContext mainserver.cpp:8030 (reconnectTimeout) MainServer: Failed to open master server socket, timeout
2017-12-10T17:59:53.861250-08:00 mythbackend[2483]: I MythSocketThread(60) mainserver.cpp:7683 (connectionClosed) Control sock(5637b922ea20) disconnected
2017-12-10T17:59:54.762026-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7981 (reconnectTimeout) MainServer: Connecting to master server: 192.168.2.141:6543
2017-12-10T17:59:54.762129-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7992 (reconnectTimeout) MainServer: Connected successfully
2017-12-10T18:00:24.881584-08:00 mythbackend[2483]: E MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal) MythSocket(5637b8fbb300:64): ReadStringList: Error, timed out after 30000 ms.
2017-12-10T18:00:24.881689-08:00 mythbackend[2483]: W MythSocketThread(-1) mainserver.cpp:7694 (connectionClosed) MainServer: Unknown socket closing MythSocket(0x5637b8fbb300)
2017-12-10T18:00:24.881784-08:00 mythbackend[2483]: E CoreContext mythsocket.cpp:369 (SendReceiveStringList) MythSocket(5637b8fbb300:-1): No response.
2017-12-10T18:00:24.881878-08:00 mythbackend[2483]: E CoreContext mainserver.cpp:8030 (reconnectTimeout) MainServer: Failed to open master server socket, timeout
2017-12-10T18:00:24.882169-08:00 mythbackend[2483]: I MythSocketThread(64) mainserver.cpp:7683 (connectionClosed) Control sock(5637b9210d10) disconnected
2017-12-10T18:00:24.882267-08:00 mythbackend[2483]: I MythSocketThread(65) mainserver.cpp:7683 (connectionClosed) Control sock(5637b9219670) disconnected
2017-12-10T18:00:25.782932-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7981 (reconnectTimeout) MainServer: Connecting to master server: 192.168.2.141:6543
2017-12-10T18:00:25.783035-08:00 mythbackend[2483]: N CoreContext mainserver.cpp:7992 (reconnectTimeout) MainServer: Connected successfully

The contents of my config.xml are:

[root@mythtv 2017-12-10]# cat /home/mythtv/.mythtv/config.xml
<Configuration>
<LocalHostName>my-unique-identifier-goes-here</LocalHostName>
<Database>
<PingHost>1</PingHost>
<Host>192.168.2.141</Host>
<UserName>mythtv</UserName>
<Password>mythtv</Password>
<DatabaseName>mythconverg</DatabaseName>
<Port>3306</Port>
</Database>
<WakeOnLAN>
<Enabled>0</Enabled>
<SQLReconnectWaitTime>0</SQLReconnectWaitTime>
<SQLConnectRetry>5</SQLConnectRetry>
<Command>echo 'WOLsqlServerCommand not set'</Command>
</WakeOnLAN>
<UPnP>
<UDN>
<MediaRenderer>4ecca28f-2f98-4ab0-b2ae-4d396ad1562d</MediaRenderer>
</UDN>
</UPnP>
</Configuration>
[root@mythtv 2017-12-10]#

Running processes are:

Code:
[root@mythtv 2017-12-10]# date; ps -aux | grep my
Sun Dec 10 18:06:16 PST 2017
root       877  0.0  0.0   4056   672 ?        Ss   17:49   0:00 runsv mythbackend
root       882  0.0  0.1  33144  2740 ?        S    17:49   0:00 su mythtv -c /usr/bin/mythbackend -q --syslog local6
root       890  0.0  0.0   4056   644 ?        Ss   17:49   0:00 runsv mysql
mythtv     897  0.0  0.2  17892  3924 ?        S    17:49   0:00 shellinaboxd -c /etc/lighttpd/ --no-beep
mythtv     948  0.0  0.6 100420 12192 ?        S    17:49   0:00 x11vnc -forever -rfbport 5902 --passwd gunther1
avahi      952  0.0  0.1  51444  3380 ?        S    17:49   0:00 avahi-daemon: running [mythtv.local]
root       956  0.0  0.1  31084  2572 ?        S    17:49   0:00 su - mythtv -l -c /usr/LH/bin/LinHES-start
mythtv    1577  0.0  0.0  17892   368 ?        S    17:49   0:00 shellinaboxd -c /etc/lighttpd/ --no-beep
root      1630  0.0  0.1  17692  3328 ?        S    17:49   0:00 /bin/sh /usr/bin/mysqld_safe --user=mysql
mythtv    1664  0.0  0.1  15444  3136 ?        Ss   17:49   0:00 /bin/sh /usr/LH/bin/LinHES-start
mythtv    1721  0.0  0.0  15956   980 ?        S    17:49   0:00 xinit /etc/X11/Sessions/LinHES -- /etc/X11/xinit/xserverrc -logverbose 6
vncsvc    1740  0.0  3.4 247296 61684 ?        Sl   17:49   0:00 /usr/bin/Xvnc :1 -auth /home/vncsvc/.Xauthority -desktop mythtv.local:1 (vncsvc) -fp /usr/share/fonts/misc,/usr/share/fonts/100dpi -geometry 1920x1080 -pn -rfbauth /home/vncsvc/.vnc/passwd -rfbport 5901 -rfbwait 30000
mysql     2045  0.1 29.1 1033300 521980 ?      Sl   17:49   0:01 /usr/bin/mysqld --basedir=/usr --datadir=/data/srv/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/data/srv/mysql/mythtv.local.err --pid-file=/data/srv/mysql/mythtv.local.pid --socket=/var/run/mysqld/mysqld.sock --port=3306
mythtv    2066  0.0  0.1  15576  3472 ?        S    17:49   0:00 /bin/bash /etc/X11/Sessions/LinHES
mythtv    2083  0.0  0.4 135208  8132 ?        S    17:49   0:00 e16 -P /usr/share/wm_data/e16_config_dir/
mythtv    2103  0.0  0.1  18064  2412 ?        S    17:49   0:00 /usr/bin/keylaunch
mythtv    2104  0.0  0.1  24324  2444 ?        S    17:49   0:00 /usr/bin/unclutter -root -idle 1 -jitter 200 -noevents
mythtv    2200  0.0  3.2 629724 59156 ?        Sl   17:49   0:00 /usr/bin/tilda -h
mythtv    2335  0.0  0.0  52256   392 ?        S    17:49   0:00 dbus-launch --autolaunch f707c8c8f35243209005bef10b0cd787 --binary-syntax --close-stderr
mythtv    2337  0.0  0.1  44944  2416 ?        Ss   17:49   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
mythtv    2340  0.0  0.2 339576  5184 ?        Sl   17:49   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
mythtv    2346  0.0  0.1  44944  3448 ?        S    17:49   0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
mythtv    2349  0.0  0.4 222344  7228 ?        Sl   17:49   0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
vncsvc    2359  0.0  0.1  15444  3048 ?        S    17:49   0:00 sh -c /home/vncsvc/.vnc/xstartup >> '/home/vncsvc/.vnc/mythtv.local:1.log' 2>&1
mythtv    2375  0.0  0.2  17692  3716 pts/0    Ss+  17:49   0:00 /bin/bash
mythtv    2483  0.1  5.7 4028836 103220 ?      Ssl  17:49   0:01 /usr/bin/mythbackend -q --syslog local6
root      2557  0.0  0.1  15440  3272 ?        S    17:50   0:00 /bin/bash /etc/cron.hourly/myth_mtc
root      2629  0.0  0.2  37448  5308 ?        Sl   17:50   0:00 tclsh /usr/bin/unbuffer myth_mtc.py --optimize
root      2630  0.0  0.0  41528  1788 ?        S    17:50   0:00 logger -t myth_mtc -p local6 info
root      2632  0.0  1.2 138616 22744 pts/1    Ss+  17:50   0:00 /usr/bin/python2 /usr/LH/bin/myth_mtc.py --optimize
mythtv    2881  1.1 12.5 2800612 224512 ?      Sl   17:50   0:10 /usr/bin/mythtv-setup
mythtv    3336  0.8  8.6 2766276 154764 ?      Sl   17:58   0:03 /usr/bin/mythfrontend -d --syslog local6
nobody    3841  0.0  0.1  11860  2672 ?        S    18:04   0:00 sh -c vmstat 300 2 1>/home/xymon/client/tmp/xymon_vmstat.mythtv.local.3695 2>&1; mv /home/xymon/client/tmp/xymon_vmstat.mythtv.local.3695 /home/xymon/client/tmp/xymon_vmstat.mythtv.local
root      3929  0.0  0.1  12576  2132 pts/2    S+   18:06   0:00 grep my
[root@mythtv 2017-12-10]#


-Jeff


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 43 posts ] 
Go to page Previous  1, 2, 3  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu