Flash Media Server and promox ve (openvz)

S

stef1777

Active Member
Jan 31, 2010
178
8
38
Hello!

Just to inform you and if someone have a an idea of the problem.

I tested Adobe Flash Media Server 4.5 r297 with promox and various config. All test done on Proxmox VE 1.8. All Debian are amd64 as FMS is only 64 bits.

openvz with Lenny + FMS4.5 + proxmox node with 2.6.18 kernel : install fine, works fine
openvz with Squeeze + FMS4.5 + proxmox node with 2.6.18 kernel : install fine, works fine
openvz with Lenny + FMS4.5 + proxmox node with 2.6.32 kernel : install fine, RTMP protocol doesn't work at all, http work
openvz with Squeeze + FMS4.5 + proxmox node with 2.6.32 kernel : install fine, RTMP protocol doesn't work at all, http work
KVM with Lenny or Squeeze + FMS4.5 + proxmox node with 2.6.32 kernel : install fine, works fine

FMS need libcap2, psmisc and libnspr4-dev packages.

The error in FMS using openvz with kernel 2.6.32 is the following:

#Date: 2011-10-11
#Fields: date time x-pid x-status x-ctx x-comment
2011-10-11 10:32:48 21182 (i)2581237 Starting admin app on core (21182). -
2011-10-11 10:32:48 21182 (i)2581238 Core (21182) connecting to admin. -
2011-10-11 10:32:48 21182 (i)2581231 Core (21182) connected to admin. -
2011-10-11 10:32:48 21182 (i)2581234 Core (21182) connection to admin accepted. -
2011-10-11 10:32:48 21182 (i)2631174 Listener started ( _defaultRoot_ ) : 127.0.0.1:19351 (rtmfp-core)/v4 -
2011-10-11 10:32:48 21182 (i)2631174 Listener started ( _defaultRoot_ ) : xxx.xxx.xxx.xxx:19351 (rtmfp-core)/v4 -
2011-10-11 10:32:48 21182 (i)2631509 Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19351;xxx.xxx.xxx.xxx:19351 -
2011-10-11 10:32:48 21182 (e)2631007 Failed to create thread (TCPollThread Ctor). -
2011-10-11 10:32:48 21182 (e)2581279 Assert failed in tincan/util/TCAsyncIO.cpp line 1036 -
2011-10-11 10:32:48 21182 (e)2631007 Failed to create thread (TCPollThread Ctor). -
2011-10-11 10:32:48 21182 (e)2581279 Assert failed in tincan/util/TCAsyncIO.cpp line 1046 -
2011-10-11 10:32:48 21182 (e)2581279 Assert failed in tincan/util/TCAsyncIO.cpp line 1051 -
2011-10-11 10:32:48 21182 (e)2581279 Assert failed in tincan/util/TCAsyncIO.cpp line 1053 -
2011-10-11 10:32:48 21182 (e)2661007 Failed to create thread (TCServerConnector::startConnector). -
2011-10-11 10:32:48 21182 (e)2581279 Assert failed in tincan/server/core/FCSBackupConnector.cpp line 81 -
2011-10-11 10:32:48 21182 (e)2571122 Server aborted. -

Each time we try to access a video using RTMP protocol, we got an error 1000 message on the client and FMS generate this message.

No real answer from Adobe support yet.
 
any fail-counts? also post 'pveversion -v'.
 
Sorry, what does you mean by "any fail-counts" ?


On the Proxmox VE 1.8 node with 2.6.18 kernel:


pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.18-6-pve
proxmox-ve-2.6.18: 1.8-15
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.18-5-pve: 2.6.18-14
pve-kernel-2.6.18-4-pve: 2.6.18-10
pve-kernel-2.6.18-6-pve: 2.6.18-15
pve-kernel-2.6.24-12-pve: 2.6.24-25
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-15


On the Proxmox VE 1.8 node with 2.6.32 kernel:


pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-3-pve: 2.6.32-13
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6
 
do you get any failcounts? or did you not understand the concept?

btw, upgrade to the latest 1.9.
 
I just read the wiki for failcnt. For the openvz VM where FMS is installed, the failcnt is 0 for all lines in /proc/user_beancounters.

I can't migrate the production cluster to 1.9 yet and I don't have an unused server to try with 1.9. I'll try to find one.
 
Hello Tom!

Good news. I tested the openvz container with a the last 1.9. RTMP seems to work with FMS now.

pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6
 
great, thanks for feedback.
 
Oops, I was not running the right kernel. Still works with kernel -6.

This show that the problem was not with the kernel but somehere in one of the openvz package.

pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6
 
Last edited:
You must log in or register to reply here.
Top Bottom