115 replies to this topic

[WanWizard]

What do you mean "no samba"?

 

For the futures version, should it be possible to create a batch for solve the samba prob's ?

 

I would like to know too if a second flash will solve it ?

 

The idea of releasing a release candidate is to get this issues to the surface, and fix them before they hit an official release. However, in two months of RC, nobody has reported this issue.

 

Just flashed a box with the latest image, and restored my autobackup. Samba works fine.

 

Weird (or should I say unexpected) thing is that is says there are 40 updates present, which should not happen when you flash the latest image. That at least suggests there is something amiss on the buildserver. After I've installed these updates and reboot the box, samba is no longer running:

/etc/init.d/samba.sh start
Starting Samba: smbd/usr/sbin/smbd: error while loading shared libraries: libsmbd-base-samba4.so: cannot open shared object file: No such file or directory
 nmbd/usr/sbin/nmbd: error while loading shared libraries: libpopt-samba3-samba4.so: cannot open shared object file: No such file or directory

This is because of the circular dependencies in the package. A second update does:

opkg upgrade
Upgrading libsamba-base from 4.4.5-r0.2 to 4.4.5-r0.4 on root.
samba was autoinstalled and is now orphaned, will remove
Removing package samba from root...
Upgrading libsamba-base (4.4.5) on root.
Downloading http://downloads.openpli.org/feeds/openpli-6-release/mips32el/libsamba-base_4.4.5-r0.4_mips32el.ipk.
Not upgrading package samba which is marked replace (flags=0x84).
Configuring libsamba-base.

After this, samba starts again:

/etc/init.d/samba.sh start
Starting Samba: smbd nmbd.

So, as mentioned before, a single update + reboot isn't enough, there might still be updates waiting after that.

[zebulon7]

So, if i understood, a second flash just after the first one will solve the problem of samba ?

[WanWizard]

Hmm...

 

I just flashed the box again, same image, and now it says "2017/10/30" on the bootlogo, and no updates are present. Samba works without problems. So I guess the flash failed in my previous attempt so the box booted with last weeks flash.

 

So, providing you don't restore or create an smb.conf that is not compatible (i.e. one you have customized for Openpli 4!) it works fine here. Both on an updated image of last week (after 2 updates + reboots !) and on a newly flashed image.

[ricki]

I had to reboot my desktop, now i can acces my shares, thanks.

[kalehrl]

Why not drop samba altogether for receivers with small flash of 128MB like my Xtrend ET6000?

It takes a huge amount of space, around 7.5MB.

I use ftp and always remove that bloat.

[WanWizard]

As you said, you can always remove it yourself. Although I am not a user as well, but appearently the majority is.

[alabama]

I think the samba problem is perhaps a timing problem.

When the desktop is up while the box starts -> it's mostly o.k.

When receiver and desktop start together sometimes I have no access with windows explorer.

[WanWizard]

No access? Or simply not visible?

 

Because those are two different things, By default Samba still uses antique netbios broadcasts to announce itself, something that isn't really supported by Windows for some time. Linux/Apple clients pick up the avahi/bonjour service broadcasts, and don't have that problem. If you see something is not related to being able to access it. You can test "\\ip-address" at Start-Run to test it.

 

Addressing this issue for Windows in on the todo list.

[alabama]

In windows explorer I defined a quicklauch with "\\IP of the box".

Sometimes, when I start Box and desktop together, I have no access.

I have a screenshot, but I cant't load the picture.

Whe I restart the box, samba access is o.k.

I can open the box over "\\IP of the box".

[WanWizard]

After the last update, that restart was necessary, to get samba started again. But that should have one a one-off only.

[velik]

Pli 6.0 release 13/10/2017. Why NO icon "REC" on VFD? For all receivers (SOLO2, DUO, UNO). Drivers?

THX!

[velik]

Pli 6.0 release 13/10/2017. Why NO icon "REC" on VFD? For all receivers (SOLO2, DUO, UNO). Drivers?

THX! 

P/S  Icon REC on VFD is not working only if Autostart Timeshift - ON. If Autostart Timeshift - OFF, then  REC is working fine.

[zebulon7]

Tonight i have flashed the last version (06/11/2017) directly by the VU+ and after the first flash, i was unable to access to the VU+Duo2 from my pc or my tablet.

 

I just flash another time and all seems to be all right now.

 

So for me, it's the solution when we have lost Samba.

 

My 2 cents...

[blunt]

Tonight i have flashed the last version (06/11/2017) directly by the VU+ and after the first flash, i was unable to access to the VU+Duo2 from my pc or my tablet.
 
I just flash another time and all seems to be all right now.
 
So for me, it's the solution when we have lost Samba.
 
My 2 cents... ;)

6/11 update is only the boot logo for me :-)

and why are you flashing everytime , just do an update not a flash everytime there's a new rev.

You'll will not loose your samba settings

Edited by blunt, 6 November 2017 - 19:02.

[Erik Slagter]

6/11 update is only the boot logo for me :-)

That will be true for many users. Don't flash or update just because you can. It's a STABLE image, don't expect real changes, only major bug fixes.

[zebulon7]

Sorry, it is what I wanted to say, actually, I did not just flashed but i make an update.

 

I think that if there is update, it is not for nothing, thus, it seems to me that it is necessary to make all the updates.