similar to: Samba 3.0.25 crash

Hi, I've been using 1.0 but moved to beta to see if it works before release. Both b14 and b15 dies sometimes when accessing folders. Last time I fixed this by moving one message from folder to another and then back. Next I'm trying to build this with debugging enabled. Tomppa > Feb 14 11:52:33 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion

Hello, was use several cad applications and with one of those we have problems using zfs. OS and hardware is SunOS 5.10 Generic_118855-36, Fire X4200, the cad application is catia v4. There are several configuration and data files stored on the server and shared via nfs to solaris and aix clients. The application is crashing on the aix client except the server is sharing those files from a ufs

Hi, I have a faulty dtrace script (most probably too big bufsize). My machine hangs at boot (amd64 5.10 Version Generic_118855-10 64-bit). NOTICE: enabling probe 11 (dtrace:::ERROR) WARNING: /etc/svc/volatile: File system full, swap space limit exceeded WARNING: Sorry, no swap space to grow stack for pid 5 (autopush) WARNING: /etc/svc/volatile: File system full, swap space limit exceeded How to

Hi, I''m running SunOS Release 5.10 Version Generic_118855-36 64-bit and in [b]/etc/system[/b] I put: [b]set zfs:zfs_nocacheflush = 1[/b] And after rebooting, I get the message: [b]sorry, variable ''zfs_nocacheflush'' is not defined in the ''zfs'' module[/b] So is this variable not available in the Solaris kernel? I''m getting really poor

I''m pretty sure this is my fault but I need some help in fixing the system. It was installed at one point with snv_29 with the pre integration SUNWzfs package. I did a live upgrade to snv_42 but forgot to remove the old SUNWzfs before I did so. When the system booted up got complaints about kstat install because I still had an old zpool kernel module lying around. So I did pkgrm

I have just recently (physically) moved a system with 16 hard drives (for the array) and 1 OS drive; and in doing so, I needed to pull out the 16 drives so that it would be light enough for me to lift. When I plugged the drives back in, initially, it went into a panic-reboot loop. After doing some digging, I deleted the file /etc/zfs/zpool.cache. When I try to import the pool using the zpool

Hello, i?ve already read many posts about checksum error on zpools but i like to have some more informations, please. We use 2 sun servers (amd x64, SunOS, 5.10 Generic_118855-36, hopefully all patches) with two hardware raids (raid 10) connected through fibre channel. Disk space is about 3 TB split into 4 pool including several (about 10 - 15) zfs each. After 22 days uptime i got a first

Hi, can anybody tell me what the errors mean and why my asterisk server falls from time to time. From time to time means several hours, not regularly. I also can provide a core if someone can debug? Thanks and regards Jan 11 14:34:59 NOTICE[13573] chan_zap.c: Hangup, did not find cref 83, tei 64 Jan 11 14:34:59 WARNING[13573] chan_zap.c: Hangup on bad channel 0/2 on span 8 Jan 11 14:35:03

Hello all, Im on the latest fresh installed centos7 with samba / winbind samba: Architektur : x86_64 Version : 4.2.10 Ausgabe : 6.el7_2 Name : samba-winbind Architektur : x86_64 Version : 4.2.10 Ausgabe : 6.el7_2 doing wbinfo -i user is working doing wbinfo -g is working doing wbinfo -u is not working and I get in winbind log: NT_STATUS_IO_TIMEOUT and Im not able to access

Hi I am wondering if this has made it into any updates? http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4645 thanks

I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

Hi, I have tested winbind in samba-3.0.25-pre2 and encountered some problems. We have a working config with Linux samba-3.0.23d and W2k3 AD R2 rfc2307bis, but when I switch to 3.0.25 it stopped working. I am not quite familiar with the new configuration directives for idmap, but the old config did not work either with 3.0.25, so I tried to use the new ones. Is there apparent errors in my config

I have several servers running Samba, all using security = ads mode. After updating one of the servers to 3.0.25, non-Kerberos login attempts now fail, although Kerberos logins work just fine. E.g.: $ smbclient -k -L //my-server OS=[Unix] Server=[Samba 3.0.25-0.0] Sharename Type Comment --------- ---- ------- ... $ smbclient -U username -L

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force

People who have reported this bug (Endless Password Expiration in 3.0.25, bugzilla id #4630) can you please let me know if you're working on 64-bit machines please ? I'm trying to track this down for 3.0.25a and am working on a theory.... Jeremy.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, For the minority of people who still run RedHat 9 or earlier, I will not be building an RPM for Samba 3.0.25 for that platform. If someone wants to pickup maintenance of it, I'll be glad to turn it over. I will leave the RedHat-9 packaging files in for the 3.0.25pre2 release that we are currently working on, but unless I hear an outcry

We've updated from 3.0.24 to 3.0.25 and we've noticed some minor problems such as some clients had to reboot in order to mount the share. And the log is now showing this warning all the time: WARNING: Winbindd not running, mapping ids with legacy code [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) We are thinking to revert to the previous version 3.0.24 which works