Problems upgrading to Samba 3.0.14a-r2!

jpnag

Hi!
I've made an emerge -uD world and I got this error when installing samba...Any ideia how I can solve this!?
Thx in advance!

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

I have a similar thing here:

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

I tried to delete "sandbox" in the FEATURES, but still got no luck emerging samba successfully

so I wonder again, how to disable the sandbox violation checking in this case?

Does anyone know?
_________________
Appreciate Gentoo: Best Devs, Best Forums. YOU could help too: Help Answer

jpnag · Posted: Sat Aug 06, 2005 8:55 am Post subject:

Do you have clamav installed?
In my case it seems a samba-vscan compilation problem not the samba itself...
_________________
Never argue with an idiot, we will drag you down to his level and beat you up with experience!

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

hi jpnag

ya, u r right, it's different, I dont have clamav installed.

jpnag · Posted: Sat Aug 06, 2005 4:16 pm Post subject:

I have tried to unmerge clamav and emerge samba but it stills not working...
I really can't figure out the reason of this error....
_________________
Never argue with an idiot, we will drag you down to his level and beat you up with experience!

[EMOBA] · n00b Joined: 07 Apr 2005 Posts: 2

I've been having to visit these forums way too much lately,and this samba mess is the last time... After tonight i'll be spending (way less) of my time on the Unbuntu forums.

Gentoo Blows!

jpnag · Posted: Sat Aug 06, 2005 5:01 pm Post subject: Re: BAAHH

r1 · n00b Joined: 07 Jul 2005 Posts: 13

Hello, I have some inputs for you:

The sandbox error is not an error but a bug, you have to log it in bugzilla http://bugs.gentoo.org . If you want to workaround this issue you can check your USE flags, I suppose you have the kerberos flag. If you don't use it you can remove it and samba will compile.

It's NOT a good idea to disable sandbox ! you can hurt your system.

r1.

jpnag

jpnag · Posted: Sat Aug 06, 2005 8:23 pm Post subject:

Ok seems the solution is:
"addpredict /etc/krb5.conf" inside src_compile function in your ebuild.
To the ones that have no ideia how to do it, just follow the steps below :wink:

Copy all files inside /usr/portage/net-fs/samba/ to /usr/local/portage/net-fs/samba/

Open "/usr/local/portage/net-fs/samba/samba-3.0.14a-r2.ebuild" with your favourite editor and add:
"addpredict /etc/krb5.conf" inside src_compile function. I added it in the 1st line.

type:
ebuild /usr/local/portage/net-fs/samba/samba-3.0.14a-r2.ebuild digest

then open your /etc/make.conf file and add the following:
PORTDIR_OVERLAY="/usr/local/portage"

finally
emerge samba

Hope this helps!
It worked for meh!

_________________
Never argue with an idiot, we will drag you down to his level and beat you up with experience!

dundas · Guru Joined: 16 Dec 2004 Posts: 317 Location: China, Earth

thx to r1 and jpnag! It worked for me.
_________________
Appreciate Gentoo: Best Devs, Best Forums. YOU could help too: Help Answer

2bbionic · Tux's lil' helper Joined: 24 Mar 2005 Posts: 97

Unfortunately, this don't work for me:

jpnag · Posted: Sun Aug 07, 2005 2:56 pm Post subject:

That does look like a problem with your system not Samba...

Just to make sure download this file copy it to your home folder or something and compile it. If u don't know how type:

2bbionic · Tux's lil' helper Joined: 24 Mar 2005 Posts: 97

Hmm...the output is "Size of short is: 2" - seems to be OK.

This is the output of tcupdate.sh:

jpnag · Posted: Sun Aug 07, 2005 4:22 pm Post subject:

I'm not sure if this will solve your problem tho I would do

2bbionic · Tux's lil' helper Joined: 24 Mar 2005 Posts: 97

I did tcupdate.sh -te without errors; but emerging samba stopped with the same error :cry:

Will Scarlet · Apprentice Joined: 19 Mar 2004 Posts: 223

Well after some searching for myself I came across these bugs:

http://bugs.gentoo.org/show_bug.cgi?id=95840
http://bugs.gentoo.org/show_bug.cgi?id=101433

Basically you have to emerge the testing version of sandbox (1.2.12 to be precise) to fix this issue without having to modify the actual ebuild for samba. For myself I just added sys-apps/sandbox ~amd64 (I have an amd64 system, use your cpu type for you system) to my package.keywords file. Hopefully they will marke sandbox version 1.2.12 stable soon so that this work around won't have to be done.

Hope this helps... :wink:

2bbionic · Tux's lil' helper Joined: 24 Mar 2005 Posts: 97

This workaround was successful! Many thanks for this great support and help!

2bbionic

njcwotx · Apprentice Joined: 24 Feb 2005 Posts: 246 Location: Texas

Execellent fix...Im past the ACCESS VIOLATION NOW!
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.

octanez · Posted: Wed Aug 17, 2005 3:34 pm Post subject:

Upgrading Sandbox worked for me

snIP3r · l33t Joined: 21 May 2004 Posts: 657 Location: germany

hi all!

i have the same problem but upgrading to sandbox ver 1.2.12 didn't fix it. do i have to recompile samba after the upgrade of sandbox??
i can only use the vscan-clamav the other shares than the home directories !?!?!?!

as user nobody i am able to access my shares (expect the home)
Aug 19 20:46:51 area52 smbd_vscan-clamav[7332]: INFO: connect to service IPC$ by user nobody
Aug 19 20:46:51 area52 smbd_vscan-clamav[7332]: INFO: disconnected

but as a normal samba user - or the one, trying to access the home i get an:

"file not found, not readable or an error occured" error

here are my config files:

[global]
log file = /var/log/samba3/log.%m
load printers = yes
smb passwd file = /etc/samba/private/smbpasswd
printer = tp0
name resolve order = wins lmhosts bcast
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
interfaces = eth0
domain master = yes
encrypt passwords = yes
public = yes
wins support = yes
dns proxy = no
netbios name = AREA52
writeable = yes
printing = cups
server string = Samba Server %v
dos charset = 850
workgroup = RESTRICTED-AREA
comment = AREA52 Drucker
printcap name = cups
security = user
unix charset = ISO8859-1
max log size = 50
log level = 1
domain logons = yes
use sendfile = no
vfs object = vscan-clamav
vscan-clamav: config-file = /etc/samba/vscan-clamav.conf

for the shares i use something like this:

[www]
comment = Webserver
# TODO config path to htdocs
path = /var/www/localhost/htdocs
read only = No
hosts allow = 192.168.0.

and here the vscan-clam.conf

[samba-vscan]
max file size = 0
verbose file logging = no
scan on open = yes
scan on close = yes
deny access on error = yes
deny access on minor error = yes
send warning message = yes
infected file action = delete
quarantine directory = /tmp
quarantine prefix = vir-
max lru files entries = 100
lru file entry lifetime = 10
clamd socket name = /var/run/clamav/clamd.sock

im using samba 3.0.14a-r2 and vscan-clamav 0.3.6.

can sb help me??

thx
snIP3r
_________________
AMD X2 3800+ on ASUS M2N-SLI Deluxe
Gentoo Base System 1.12.11.1
Kernel 2.6.29-gentoo-r5 SMP x86_64
-----------------------------------------------
if your problem is fixed please add something like [solved] to the topic!

MerryConqueror · n00b Joined: 28 Jul 2003 Posts: 3

Just to add a data point: I also had this problem, and the sandbox upgrade did fix it for me.

Will Scarlet · Apprentice Joined: 19 Mar 2004 Posts: 223

Well, it seem that sandbox-1.2.12 is now considered stable on x86, amd64, ppc, ppc64, hppa, sparc, and alpha . After reviewing the ChangeLog, I discovered that it went stablel on 15 Aug. I would suggest that anyone with any of the above architectures that modified there package.keywords file with sys-apps/sandbox ~(your arch here) to comment that line out.

Edit: added architectures that are considered stable as of 15 Sept 2005.

To snIP3r:

As you already have samba-3.0.14a-r2 on your system compiled fine, your problem was not with the sandbox issue. I would suggest that you open a different post.

Hope this helps... :wink:

Jovana · n00b Joined: 23 Nov 2005 Posts: 53

emerge sandbox did the trick. Thanks for your help and suggestions.