Jump to content


Photo

VU+ SoloSe v2 crashing constantly


  • Please log in to reply
36 replies to this topic

#1 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 22 January 2019 - 17:24

Hi Everyone

 

I'm using OpenPLI on my VU+ SoloSe v2 for 2 years and a half already. Now i updated it to the latest stable version 7.0 from 16.1.2019 with OSCam r11466 and my provider's Conax card in lower card port. The box is practicaly all the time used for streaming 1 or 2 channels to the remote TV's over WLAN network where channels are watched on Kodi and Computer with VLC.

 

From the very beggining (2,5 years back) i'm having problems with occasional crashes of the box. Occasionaly WEB interface becomes unresponsive and sometimes i can still reset it through SSH, other times even SSH stop's working and i have to pull the plug to make it work again. There is no sign when this will happen. Sometimes it works fine for 2 weeks, other times it crashes every day. I think it's more often when channels are encoded but i'm not completly sure in that. 

 

Is there any way i could get a .log file out of device after it has been reset to see what happened or even all log files are reset?  Any other sugestions what could be wrong? 

 

Thank you

 

Daniel


Edited by DinDin, 22 January 2019 - 17:25.


Re: VU+ SoloSe v2 crashing constantly #2 WanWizard

  • Forum Moderator
    PLi® Core member
  • 47,552 posts

+797
Excellent

Posted 22 January 2019 - 17:34

Chances are it's just running out of memory due to memory fragmentation in the drivers. 

 

Next time this happens, and you can still log in, do so, issue the command "dmesg", and post the last 50 or so lines here.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ SoloSe v2 crashing constantly #3 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 22 January 2019 - 18:08

Ok, i will do that. Thank you.

 

This is the current state, when it's working ok:

root@vusolose:~# dmesg
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 17
Key type dns_resolver registered
PM: CP0 COUNT/COMPARE frequency does not depend on divisor
EBI CS0: setting up NAND flash (primary)
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix H27U4G8F2DTR-BC)
NAND device: 512MiB, SLC, page size: 2048, OOB size: 64
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix H27U4G8F2DTR-BC)
NAND device: 512MiB, SLC, page size: 2048, OOB size: 64
brcmnand brcmnand.0: 512MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
Bad block table found at page 261824, version 0x01
Bad block table found at page 261760, version 0x01
nand_read_bbt: bad block at 0x000000bc0000
nand_read_bbt: bad block at 0x00000b800000
nand_read_bbt: bad block at 0x00000c1e0000
nand_read_bbt: bad block at 0x00001de80000
nand_read_bbt: bad block at 0x00001ec20000
nand_read_bbt: bad block at 0x00001ff80000
nand_read_bbt: bad block at 0x00001ffa0000
nand_read_bbt: bad block at 0x00001ffc0000
nand_read_bbt: bad block at 0x00001ffe0000
Creating 4 MTD partitions on "brcmnand.0":
0x000001f00000-0x000020000000 : "rootfs"
0x000001f00000-0x000020000000 : "rootfs(redundant)"
0x000000200000-0x000000900000 : "kernel"
0x000000900000-0x000000a00000 : "mac"
UBI: attaching mtd0 to ubi0
random: nonblocking pool is initialized
scsi 3:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 0 CCS
sd 3:0:0:0: Attached scsi generic sg0 type 0
UBI: scanning is finished
UBI: attached mtd0 (name "rootfs", size 481 MiB) to ubi0
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 3836, bad PEBs: 12, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 161/79, WL threshold: 4096, image sequence number: 1516618653
UBI: available PEBs: 0, total reserved PEBs: 3836, PEBs reserved for bad PEB handling: 68
UBI: background thread "ubi_bgt0d" started, PID 56
ALSA device list:
  No soundcards found.
sd 3:0:0:0: [sda] 31277056 512-byte logical blocks: (16.0 GB/14.9 GiB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 23 00 00 00
sd 3:0:0:0: [sda] No Caching mode page found
sd 3:0:0:0: [sda] Assuming drive cache: write through
sd 3:0:0:0: [sda] No Caching mode page found
sd 3:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 3:0:0:0: [sda] No Caching mode page found
sd 3:0:0:0: [sda] Assuming drive cache: write through
sd 3:0:0:0: [sda] Attached SCSI removable disk
UBIFS: parse sync
UBIFS: background thread "ubifs_bgt0_0" started, PID 59
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS: FS size: 476540928 bytes (454 MiB, 3753 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
UBIFS: reserved for root: 0 bytes (0 KiB)
UBIFS: media format: w4/r0 (latest is w4/r0), UUID 731B89D0-D69E-4B00-B75A-2AC581179013, small LPT model
VFS: Mounted root (ubifs filesystem) on device 0:12.
devtmpfs: mounted
Freeing unused kernel memory: 256K (80740000 - 80780000)
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
procmk_init
dvb_bcm7241: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (_vuplus_solose_)
bcm7241: hotplug_callback():
Hotplug - status.connected 1:0:0
bcm7241: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
[GPIO]Default
bcm7241: hotplug_callback():
Hotplug - status.connected 1:1:2
brcm_demux_init: $Id: bcm_demux.c,v 0.7 $
[MPVR]: >> misc_pvr_init
[VID]: 6bcm7335_video_init
[AUD]: 6bcm7335_audio_init
BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (Vuplus FE)...
BRCM brcm_dvb0: DVB: registering adapter 0 frontend 0 (Vuplus FE)...
bcm7241: bcm7335_frontend_init(): vtuner1 : 3
BKNI_P_GetTrackAllocEntry_resize: resizing from 5376->8704
BKNI_Malloc(linuxkernel) top users:
    blocks,   bytes, filename:line
      1024,  176128, portinginterface/hsm/src/common/bhsm.c:500
       838,  190952, BSEAV/lib/utils/balloc.c:31
       346,   22144, magnum/commonutils/mrc/src/bmrc_monitor.c:666
  KSEG1 : 0x80000000
input: dreambox advanced remote control (native) as /devices/virtual/input/input0
[LCD]: registered
0:0
[CI]: registered ci0
[CI]: CI interface initialised

[DFP]: registered dbox fp
[DFP]: Scart 4710 is found 4

[SC]: registered sci0
system_time_set wakeup mode get
system_time_set wakeup mode get 0xc4
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_SELECT_SOURCE 1  0
[VID]: VIDEO_PLAY 1  5 0
[VID]: VIDEO_CONTINUE 1  1
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0  0
__clk_enable: network [1]
bcm7429_pm_network_enable 00
__clk_enable: enet [1]
bcm40nm_pm_genet_enable 00
bcmgenet bcmgenet.0 eth0: link up, 100 Mbps, full duplex
bcmgenet bcmgenet.0 eth0: link down
bcmgenet bcmgenet.0 eth0: link up, 100 Mbps, full duplex
NET: Registered protocol family 10
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_SELECT_SOURCE 1  0
[VID]: VIDEO_PLAY 1  5 0
[VID]: VIDEO_CONTINUE 1  1
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0  0
UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
[SC]: !!!unknown cmd 0x5407
[AUD]: AUDIO_SET_MUTE 0
[AUD]: AUDIO_SET_MIXER -818209296
[AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
[AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
[AUD]: AUDIO_SET_MIXER : next left volume -210, right volume -210
[AUD]: AUDIO_SET_MUTE 1
[AUD]: AUDIO_SET_MIXER -818209296
[AUD]: AUDIO_SET_MIXER : amixl 7, amixr 7
[AUD]: AUDIO_SET_MIXER : next left volume -210, right volume -210
[AUD]: AUDIO_SET_MIXER : next left volume -710, right volume -710
FE tune
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_GET_SIZE src w: 1920 h:1080 display w:1920 h:1080
[VID]: VIDEO_GET_SIZE aspect: 1 6
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 2143594928  0
[VID]: VIDEO_PLAY 2143594928  2 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xcb924480
[AUD]: Mute : 1
[AUD]: AUDIO_CHANNEL_SELECT 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP -2
[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
FE tune
[AUD]: AUDIO_SET_MUTE 0
bcm7241: hotplug_callback():
Hotplug - status.connected 1:1:2
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 2143589472  0
[VID]: VIDEO_PLAY 2143589472  2 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xcb9b7200
[AUD]: Mute : 0
[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[VID]: VIDEO_GET_SIZE aspect: 1 0
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xcb9b7200
[AUD]: Mute : 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP -2
[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 2143590744  0
[VID]: VIDEO_PLAY 2143590744  2 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xcb9c6f80
[AUD]: Mute : 0
[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[VID]: VIDEO_GET_SIZE aspect: 1 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP -2
[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 2143590744  0
[VID]: VIDEO_PLAY 2143590744  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xc5cd9900
[AUD]: Mute : 0
[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[VID]: VIDEO_GET_SIZE aspect: 1 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP -2
[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 2143590744  0
[VID]: VIDEO_PLAY 2143590744  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xcb9e4880
[AUD]: Mute : 0
[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[VID]: VIDEO_GET_SIZE aspect: 1 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP -2
[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 1
[AUD]: AUDIO_PLAY 1 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0  0
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 2143589480  0
[VID]: VIDEO_PLAY 2143589480  2 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xc5cda780
[AUD]: Mute : 0
[VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
[VID]: VIDEO_GET_SIZE aspect: 1 0
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 0  1
[AUD]: AUDIO_CONTINUE 0 1 aph=0xc5cda780
[AUD]: Mute : 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP -2
[AUD]: AUDIO_CONTINUE -2 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0

Edited by DinDin, 22 January 2019 - 18:12.


Re: VU+ SoloSe v2 crashing constantly #4 WanWizard

  • Forum Moderator
    PLi® Core member
  • 47,552 posts

+797
Excellent

Posted 22 January 2019 - 18:34

You might want to look at:

FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

either on the commandline or using "File system check" in the Harddisk menu.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ SoloSe v2 crashing constantly #5 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 22 January 2019 - 19:50

That is probably USB thumb drive that i used for flashing, otherwise it wasn't connected before and utill now it was formatted in fat32. Now system has formated it to what it uses (ext3 or 4).



Re: VU+ SoloSe v2 crashing constantly #6 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 23 January 2019 - 19:31

It just hanged itself, but this time totally. No way to ssh into, waiting for another chance. Is there any way to export the log on the fly as it happens to some file on network or something? Or maybe direct connection to RX an TX in the board?

Re: VU+ SoloSe v2 crashing constantly #7 Erik Slagter

  • PLi® Core member
  • 45,263 posts

+497
Excellent

Posted 23 January 2019 - 19:39

The best solution for this sort of problems is to schedule a restart every day (or night).


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: VU+ SoloSe v2 crashing constantly #8 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 23 January 2019 - 20:27

Well now it worked 30 minutes and hanged again, without ssh acess, so i doubt a bit, that scheduled restart would help. Maybe a deamon who checks if system is unresponsive and reboots automaticaly would be better.



Re: VU+ SoloSe v2 crashing constantly #9 ims

  • PLi® Core member
  • 11,111 posts

+167
Excellent

Posted 23 January 2019 - 20:33

Did you try power source ? Or measured under load ?


Kdo nic nedělá, nic nezkazí!

Re: VU+ SoloSe v2 crashing constantly #10 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 23 January 2019 - 20:46

No, i did not yet. It's a good idea to check it. When it hangs, the device still stays very warm to touch (it has small heatsing). CPU usage is practicaly nothing, what streaming two channels.

Mem: 161600K used, 509900K free, 116K shrd, 40K buff, 58752K cached
CPU:   0% usr   0% sys   0% nic 100% idle   0% io   0% irq   0% sirq
Load average: 1.17 1.10 0.92 2/103 4221
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
    3     2 root     SW       0   0%   0% [ksoftirqd/0]
  479   474 root     S     115m  18%   0% /usr/bin/enigma2
  508     1 root     S    96856  14%   0% /usr/local/hbb-browser/lib/hbbtv.app r
  435     1 root     S    33196   5%   0% /usr/sbin/smbd
  437   435 root     S    31736   5%   0% {smbd-notifyd} /usr/sbin/smbd
  438   435 root     S    31728   5%   0% {cleanupd} /usr/sbin/smbd
  440     1 root     S    21536   3%   0% /usr/sbin/nmbd
  470   468 root     S <  16052   2%   0% /usr/bin/oscam --wait 0 --config-dir /
  468     1 root     S     6900   1%   0% /usr/bin/oscam --wait 0 --config-dir /
  465     1 root     S     5828   1%   0% /usr/bin/streamproxy
  461     1 avahi    S     3892   1%   0% avahi-daemon: running [vusolose.local]
  462   461 avahi    S     3772   1%   0% avahi-daemon: chroot helper
 1877  1847 root     S     3292   0%   0% -sh
  402     1 messageb S     3236   0%   0% /usr/bin/dbus-daemon --system
  418     1 rpcuser  S     3180   0%   0% /usr/sbin/rpc.statd
  422     1 root     S     3172   0%   0% /usr/sbin/inetd
 3162  3161 root     S     3036   0%   0% -sh
  454     1 root     S     3036   0%   0% /sbin/klogd -n
  451     1 root     S     3036   0%   0% /sbin/syslogd -n -O /var/log/messages
  391     1 root     S     3036   0%   0% udhcpc -b -H vusolose -p /var/run/udhc

Edited by DinDin, 23 January 2019 - 20:46.


Re: VU+ SoloSe v2 crashing constantly #11 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 23 January 2019 - 20:48

Aaaaaand it hanged again, and again without SSH.



Re: VU+ SoloSe v2 crashing constantly #12 ccs

  • Senior Member
  • 82 posts

+2
Neutral

Posted 23 January 2019 - 20:53

Can't you switch on debug logs and grab the log file as soon as the box has been rebooted?



Re: VU+ SoloSe v2 crashing constantly #13 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 23 January 2019 - 21:01

How can you do that? 

 

Could the issue be connected to overheating even if CPU is practicly not in use?



Re: VU+ SoloSe v2 crashing constantly #14 WanWizard

  • Forum Moderator
    PLi® Core member
  • 47,552 posts

+797
Excellent

Posted 23 January 2019 - 21:21

Start the box, telnet into it, stop Enigma with 

init 4

start again in debug mode with

ENIGMA_DEBUG_LVL=4 enigma2

leave the log running over your open telnet session, and wait until it crashes. Then post the last log entries here.

 

If you use something like PuTTY, you can configure it to create a logfile as well, so you have all output, not only the last few log lines.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: VU+ SoloSe v2 crashing constantly #15 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 23 January 2019 - 21:49

Great, i will do that. I disasembled the box now and put fresh thermal paste on CPU and screwed cooling fins back with a nylon screw instead of spring assisted bolt that let the fins move if you touched them. Temperature is currently arround 50 degrees with 2 streams running.



Re: VU+ SoloSe v2 crashing constantly #16 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 24 January 2019 - 03:38

Well, that is odd. Device stopped reponding again, no network reply, it doesn't respond to remote, nothing. But in the log, i don't see anthing realy.

 

Complete paste on Pastebin:

 

https://pastebin.com/qSw21ZY5



Re: VU+ SoloSe v2 crashing constantly #17 betacentauri

  • PLi® Core member
  • 5,247 posts

+244
Excellent

Posted 24 January 2019 - 07:11

Login again via telnet and this time please execute
tail -f /var/log/messages

Wait until the box crashes again.

Edited by betacentauri, 24 January 2019 - 07:13.

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: VU+ SoloSe v2 crashing constantly #18 Taykun345

  • Senior Member
  • 1,154 posts

+31
Good

Posted 24 January 2019 - 09:27

Well now it worked 30 minutes and hanged again, without ssh acess, so i doubt a bit, that scheduled restart would help. Maybe a deamon who checks if system is unresponsive and reboots automaticaly would be better.

 

It hangs completely or you still have sound in the background? My Duo2 started to have random freezes. Audio still worked but everything else was frozen, SSH access not possible. There are other reports of same problem, MB replacement is needed.


Army MoodBlue HD skin modification by me: https://github.com/T...-MoodBlueHD-mod
Matrix10 MH-HD2 skin modification by me: https://github.com/B...-MX-HD2-OpenPli
MetrixHD skin modification by me: https://github.com/T...xHD-WPstyle-mod
Slovenian translation for OpenPLi E2: https://github.com/T...ion-for-OpenPLi

Re: VU+ SoloSe v2 crashing constantly #19 DinDin

  • Senior Member
  • 26 posts

0
Neutral

Posted 24 January 2019 - 15:14

I wouldn't realy know because im only using it to stream 2 channels, i don't watch anything with him (i would if it would have FBC tuner). Until now it still works and telnet is waiting if anything will happen. I think i may gonna need RS232 cable. Does anyone know if SoloSE have internal header for serial connection? There are three free headers inside, but no usable information besides them. One 4 PIN is named P105.



Re: VU+ SoloSe v2 crashing constantly #20 Erik Slagter

  • PLi® Core member
  • 45,263 posts

+497
Excellent

Posted 24 January 2019 - 16:36

Start the box, telnet into it, stop Enigma with 

init 4

start again in debug mode with

ENIGMA_DEBUG_LVL=4 enigma2

leave the log running over your open telnet session, and wait until it crashes. Then post the last log entries here.

 

If you use something like PuTTY, you can configure it to create a logfile as well, so you have all output, not only the last few log lines.

Total hangups caused by enigma?


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users