Displaying 20 results from an estimated 70000 matches similar to: "3.2.4 CreateDirectory panic"
2008 Oct 17
2
problem usrmgr Version 3.2.4
hi , i have
a few problems with usmgr on Version 3.2.4
( Version 3.2.4-8.1-1931-SUSE-SL11.0 )
samba pdc ldap
the download version from ms
http://www.microsoft.com/Downloads/details.aspx?FamilyID=c0011ab8-3178-4701-a791-eafba0f42de2&displaylang=en
doesnt work
giving
"device attached to the system is not functioning"
whatever i do
a old version from usermgr works partially
but magic
2008 Dec 15
2
rsync 3.0.4 ACL corruption
Hi,
I use rsync 3.0.4 on two opensuse 11 machines.
Every night, a big tree of machine A is synced to machine B.
These machines are samba PDC and BDC, users and groups are ldap-based,
and ACLs are heavily used. There are about 2.8 million files and dirs,
2.2 terabytes of data, and a complete ACL list produced with getfacl has
some 600 megabytes.
I've just noticed that ACLs get partially
2008 Nov 04
3
3.2.4 ACL inheritance trouble
Hi,
Since 3.2.4 (maybe earlier, but I doubt it), one important feature does
not work anymore for me:
I cannot break ACL inheritance anymore in the Windows ACL editor. With
previous Samba versions, I entered the "Advanced" dialog of the Windows
ACL editor and unchecked the flag "Inherit from parent the permission
entries that apply to child objects. Include these with entries
2010 Jul 15
3
Windows 7 machine trust accounts expiring
There was an earlier thread about failing trust relationships between
Windows 7 and Samba. Since we occasionally experience the same problem
with Win 7 clients against a Samba 3.5.4 server, I investigated this a
bit further.
I think it happens when
- the time to change the machine password has arrived
- the Win 7 machine is up, but no one is logged on (login box is shown
on the screen).
To
2020 Jan 28
2
imap panic: file array.c: line 10 (array_idx_modifiable_i)
??????? Original Message ???????
On Tuesday, January 28, 2020 9:06 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote:
> doveadm does not travel over namespace boundaries. you need to run it separately for all namespaces you have with NAMESPACE/* as folder
I see, so with my following namespace config:
namespace inbox {
separator = .
prefix = INBOX.
inbox = yes
}
I should use the
2017 Sep 17
1
dsync panic in mbox_lock
Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
> We have seen this before but so far the actual bug has not been
> reproducible for us. Can you post your doveconf -n
Here it is:
https://ftp.espci.fr/shadow/manu/conf.log
> and also logs with
> doveadm -Dv -o plugin/mail_replica=remoteprefix:root at mail2.example.net
> sync -d -u jdoe
https://ftp.espci.fr/shadow/manu/sync.log
2018 Aug 22
0
lmtp Panic Buffer write out of range
Op 21-8-2018 om 14:57 schreef Gabriele Nencioni:
> Hi all,
> as described here:
> https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html
>
> we are experiencing the same error on dovecot version 2.3.2.1
> while it never occurs on an old version as 2.2.15
This looks a lot like:
https://dovecot.org/list/dovecot/2018-July/112167.html
That one is fixed pending release.
2013 Nov 15
0
Dovecot panic during replication
I'm seeing the following errors on my Dovecot box when trying to replicate:
Nov 15 18:44:46 server1 dovecot: dsync-server(mark): Panic: file
mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK
|| mbox->mbox_lock_type != F_RDLCK)
Nov 15 18:44:46 server1 dovecot: dsync-server(mark): Fatal: master:
service(doveadm): child 21571 killed with signal 6 (core not dumped -
2017 Feb 27
1
Fwd: Some mails do not get replicated anymore after memory-exhaust
Hey guys,
overall I have an working dovecot replication between 2 servers running on
amazon cloud. Sadly I had some messages that my server ran out of memory.
After investigating a little bit further I realized that some mails didn't
got replicated, but I'm not sure if this was related to the memory exhaust.
I was expecting that the full-sync would catch them up but sadly it's not.
2020 Oct 12
0
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div class="default-style">
Replication is not supported with mbox format. You can only do unidirectional sync out of mbox.
</div>
<div class="default-style">
<br>
</div>
<div
2018 Feb 19
0
[bt full included] imap-login: Panic: file client-common.c: line 272 (client_destroy): assertion failed: (client->create_finished)
Hi,
as discussed with cmouse on freenode two days ago please find attached
necessary debug information on a crashing imap-login process, that
appeared after upgrading to v2.3 (+ sieve). It is a standard setup in
combination with postfix and thunderbird, roundcube and K9(Android) as
imap clients. Panic happens 5-6 times a day, but no influence on user
experience. Unfortunately i have no idea
2018 Aug 21
2
lmtp Panic Buffer write out of range
Hi all,
as described here:
https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html
we are experiencing the same error on dovecot version 2.3.2.1
while it never occurs on an old version as 2.2.15
It followings the error logs:
On an upgraded dovecot backend:
Aug 21 12:03:51 backend20 dovecot:
lmtp(test1 at internalinboundcm.eu)<SONkAYfje1veGgAAu8+/vw>: Panic: Buffer
write out of
2017 Sep 16
0
dsync panic in mbox_lock
> On September 16, 2017 at 5:28 AM Emmanuel Dreyfus <manu at netbsd.org> wrote:
>
>
> Hello
>
> I am trying to setup replication with dovecot-2.2.29.1, and for some
> users, I get a reproductible panic:
>
> # doveadm -v -o plugin/mail_replica=remoteprefix:root at mail2.example.net
> sync -d -u jdoe
> dsync-local(jdoe): Panic: file mbox-lock.c: line 799
2020 Jan 28
0
imap panic: file array.c: line 10 (array_idx_modifiable_i)
> On 28 Jan 2020, at 10.31, mabi <mabi at protonmail.ch> wrote:
>
> ??????? Original Message ???????
> On Tuesday, January 28, 2020 9:06 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote:
>
>> doveadm does not travel over namespace boundaries. you need to run it separately for all namespaces you have with NAMESPACE/* as folder
>
> I see, so with my
2020 Jan 28
2
imap panic: file array.c: line 10 (array_idx_modifiable_i)
??????? Original Message ???????
On Monday, January 27, 2020 8:37 AM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
> You could try force-resync, it is safe to run.
>
> Anyways, without backtrace from core file it's hard to say.
Hi Aki,
I now ran the following command to force resync all mailboxes:
sudo doveadm -Dv force-resync -u email at domain.com \*
and this gave the
2012 Jan 31
0
Error in linearHypothesis.mlm: The error SSP matrix is apparently of deficient rank
Hi,
I have encountered this error when attempting a One-way Repeated-measure ANOVA
with my data.
I have read the "Anova in car: SSPE apparently deficient rank" thread
by I'm not sure the within-subject interaction has more degrees of freedom
than subjects in my case.
I have prepared the following testing script:
rm(list = ls())
2017 Sep 28
1
doveadm backup panic, dsync-ibc.c, dsync_ibc_send_mailbox_tree_node, assertion failed: (*name != NULL)
Hi folks,
Not sure how much extra information I'll be able to provide on this, but
I'm experiencing a consistent, reproducible dsync backup error with a
single, specific account I'm trying to migrate from UW-IMAP / Panda (mix
mailbox) to a Dovecot 2.2.32 cluster. Didn't spot any core files laying
around.
Doveadm backup output, dovecot --version and dovecot -n below:
2015 Aug 19
3
Centos7 Kernel Panic
Hello Everyone,
I have prepared following isolinux.cfg.
default linux
label linux
kernel /vmlinuz
append initrd=/initrd.gz
But kernel panics with the standard message 'Kernel panic - not syncing: No
init found'.
Linux kernel version is 3.10.
I tried to read the init.txt too.But could not figure out the issue.
Can you please help me figure out the problem ?
Thanks
Sachin
2015 Dec 05
0
7.2 kernel panic on boot
I always admire Johnny's prose, passion for Centos and his calm approach
to everything.
He is right. We are stuck with the numbering system.
On Sat, 2015-12-05 at 12:46 -0600, Johnny Hughes wrote:
> The bottom line is, our numbering system works for us to be able to do
> all those things.
>
> This is much more complicated than just a name on an ISO and I don't
> think
2008 Sep 25
1
Fwd: Re: Samba 3.2.4 and alternate data streams
To be honest, I'm not sure wether these alternate data stream files were
created under 3.2.0 3.2.2 or 3.2.4.
I just noticed that they are here and report.
How can I make sure that these files will not be created again (some kind
of test case that records alternate data streams) ?
Is there any possibility to disable this alternate data stream feature ?
Fran?ois
-------- Original Message