Samba Error - Can´t Record IP Camera Video to WD

[salvaterra]

Dear friends, I have a Vivotek IP7330 camera and i´m having issues while trying to record video to my wd my book live. Both the camera and the mybook have the latest firmware.

Just to let you know, I have three cameras, two can record without issues, the vivotek can´t. Previously i had a WD Mybook World which would work with all three cameras without issues.

When the vivotek tries to record to samba server, i file with 0kb (zero) is recorded to the choosen folder. If I use the ftp server of the wd mybook live, it works flawlessly.

Here´s the wd mybook live log output when the camera attempts to send video:

Jun 6 06:59:48 hd smbd[18866]: [2013/06/06 06:59:48.112026, 0] lib/util.c:1117(smb_panic)
Jun 6 06:59:48 hd smbd[18866]: PANIC (pid 18866): failed to drain pending bytes
Jun 6 06:59:48 hd smbd[18866]: [2013/06/06 06:59:48.196553, 0] lib/util.c:1221(log_stack_trace)
Jun 6 06:59:48 hd smbd[18866]: BACKTRACE: 14 stack frames:
Jun 6 06:59:48 hd smbd[18866]: #0 /usr/sbin/smbd(log_stack_trace+0x40) [0x206e2634]
Jun 6 06:59:48 hd smbd[18866]: #1 /usr/sbin/smbd(smb_panic+0x7c) [0x206e2780]
Jun 6 06:59:48 hd smbd[18866]: #2 /usr/sbin/smbd(+0x1f58c4) [0x204058c4]
Jun 6 06:59:48 hd smbd[18866]: #3 /usr/sbin/smbd(+0x1f5b84) [0x20405b84]
Jun 6 06:59:48 hd smbd[18866]: #4 /usr/sbin/smbd(+0x1f5bf8) [0x20405bf8]
Jun 6 06:59:48 hd smbd[18866]: #5 /usr/sbin/smbd(run_events_poll+0x484) [0x206f3928]
Jun 6 06:59:48 hd smbd[18866]: #6 /usr/sbin/smbd(smbd_process+0x970) [0x20405580]
Jun 6 06:59:48 hd smbd[18866]: #7 /usr/sbin/smbd(+0x77b0a4) [0x2098b0a4]
Jun 6 06:59:48 hd smbd[18866]: #8 /usr/sbin/smbd(run_events_poll+0x484) [0x206f3928]
Jun 6 06:59:48 hd smbd[18866]: #9 /usr/sbin/smbd(+0x4e3de8) [0x206f3de8]
Jun 6 06:59:48 hd smbd[18866]: #10 /usr/sbin/smbd(_tevent_loop_once+0xc4) [0x206f4378]
Jun 6 06:59:48 hd smbd[18866]: #11 /usr/sbin/smbd(main+0x1234) [0x2098c864]
Jun 6 06:59:48 hd smbd[18866]: #12 /lib/libc.so.6(+0x1f63c) [0x1fa9f63c]
Jun 6 06:59:48 hd smbd[18866]: #13 /lib/libc.so.6(+0x1f800) [0x1fa9f800]
Jun 6 06:59:48 hd smbd[18866]: [2013/06/06 06:59:48.199996, 0] lib/fault.c:372(dump_core)
Jun 6 06:59:48 hd smbd[18866]: dumping core in /var/log/samba/cores/smbd

I found a thread in another forum where a user has a similar problem with a different product and they found a solution, however it does not work for wd mybook live:

http://forum.qnap.com/viewtopic.php?p=250644

They figured out that the two equipments were running different samba versions.

Any help will be really apreciated.

[nfodiz]

This is a real shot in the dark but worth a try if you know how to SSH into the drive

Turn on SSH on the MBL by opening your web browser and going to the dashboard at

your mbl name or ip/UI/ssh

SSH into the MBL using PuTTY (Windows) or Terminal (Built into the Mac)

http://winscp.net/download/winscp510setup.exe

Enter the MBL network name or IP in the PUTTY window

username: root

password : welc0me

If you are using MAC Terminal you simply type (replace your MBLl name or ip after the @)

ssh root@your mybooklive network name.local

once logged in type

nano /etc/samba/smb-global.conf

REMOVE “max protocol = SMB2” from the bottom of the file and save it by hitting

control and o

press enter

control and x

The MyBookLive will now default to Samba v1

Reboot the MBL for the changes to take effect OR simply restart the samba service

/etc/init.d/samba restart

If still no go, just revert the changes

[salvaterra]

Dear Nfodiz,

Thanks for your reply, however it did not work. Still getting this log output:

Jun 6 19:04:35 hd smbd[6262]: [2013/06/06 19:04:35.934918, 0] lib/util.c:1117(smb_panic)
Jun 6 19:04:35 hd smbd[6262]: PANIC (pid 6262): failed to drain pending bytes
Jun 6 19:04:35 hd smbd[6262]: [2013/06/06 19:04:35.945885, 0] lib/util.c:1221(log_stack_trace)
Jun 6 19:04:35 hd smbd[6262]: BACKTRACE: 14 stack frames:
Jun 6 19:04:35 hd smbd[6262]: #0 /usr/sbin/smbd(log_stack_trace+0x40) [0x20c62634]
Jun 6 19:04:35 hd smbd[6262]: #1 /usr/sbin/smbd(smb_panic+0x7c) [0x20c62780]
Jun 6 19:04:35 hd smbd[6262]: #2 /usr/sbin/smbd(+0x1f58c4) [0x209858c4]
Jun 6 19:04:35 hd smbd[6262]: #3 /usr/sbin/smbd(+0x1f5b84) [0x20985b84]
Jun 6 19:04:35 hd smbd[6262]: #4 /usr/sbin/smbd(+0x1f5bf8) [0x20985bf8]
Jun 6 19:04:35 hd smbd[6262]: #5 /usr/sbin/smbd(run_events_poll+0x484) [0x20c73928]
Jun 6 19:04:35 hd smbd[6262]: #6 /usr/sbin/smbd(smbd_process+0x970) [0x20985580]
Jun 6 19:04:35 hd smbd[6262]: #7 /usr/sbin/smbd(+0x77b0a4) [0x20f0b0a4]
Jun 6 19:04:35 hd smbd[6262]: #8 /usr/sbin/smbd(run_events_poll+0x484) [0x20c73928]
Jun 6 19:04:35 hd smbd[6262]: #9 /usr/sbin/smbd(+0x4e3de8) [0x20c73de8]
Jun 6 19:04:35 hd smbd[6262]: #10 /usr/sbin/smbd(_tevent_loop_once+0xc4) [0x20c74378]
Jun 6 19:04:35 hd smbd[6262]: #11 /usr/sbin/smbd(main+0x1234) [0x20f0c864]
Jun 6 19:04:35 hd smbd[6262]: #12 /lib/libc.so.6(+0x1f63c) [0x2001f63c]
Jun 6 19:04:35 hd smbd[6262]: #13 /lib/libc.so.6(+0x1f800) [0x2001f800]
Jun 6 19:04:35 hd smbd[6262]: [2013/06/06 19:04:35.949058, 0] lib/fault.c:372(dump_core)
Jun 6 19:04:35 hd smbd[6262]: dumping core in /var/log/samba/cores/smbd

Any other ideas?

[nfodiz]

Darn, was hoping that might do the trick. Firmware 02.11.09-053 runs an older samba stack than the last 3 or so firmwares. It might be worth a shot downgrading to that firmware to see if it makes a difference.

http://community.wd.com/t5/My-Book-Live/GUIDE-Restore-Downgrade-firmware-via-the-reset-button/m-p/481588

[salvaterra]

Dear nfodiz,

I would like to thank you again for your help and patience.

I flash the firmware you mentioned, but still no luck. After flashing, I tried editing the smb-global.conf and the “max protocol = SMB2” line wasn´t there. I even tried to put it back and restart samba, however it still does not work.

Any other help will be really appreciated.

[nfodiz]

That’s all I can think of. I did a little googling but didn’t come up with much. Maybe someone else will jump in with a solution

[salvaterra]

Dear Nfodiz,

Could you give me a hint?

How do I check which samba protocol is running at the moment? just to make sure it changed to V1.

[nfodiz]

I had to use Wireshark to make sure but trust me, when you change that line it defaults to Samba v1. I talked with TonyPh12345 and he and I believe you have run into some sort of Samba bug.

[salvaterra]

Nfodiz,

Thanks for all your help. I have sent this issue to Western Digital technical support as well as Vivotek, if I figure out a solution I will post it here.

Thanks again.

[salvaterra]

Dear Nfodiz,

I have contect Vivotek techical support. The access my computer via Teamviewer and tried to figure out a solution.

They concluded that there´s a incompatibility issue between Vivotek IP7330 and MBL and they can´t fix it because the camera is phase-out.

[nfodiz]

Yeah I believe that… I doubt WD will be able to issue a fix either if it is a Samba bug you have stumbled across. I don’t see them upgrading the Samba stack on the MyBookLive again but I could be wrong.