Discussion:
[unison-users] Unison Error
Maksim Kopachovets m.kopachovets@gmail.com [unison-users]
2017-07-05 10:37:53 UTC
Permalink
Good afternoon. After upgrading to version 2.48.4, when trying to
synchronize produces an error: Fatal error: Server error files: error error
23 while adding a watcher The watcher can be disabled by setting preference
'watch' to false My configuration file:
root = /data/ root = socket://192.168.2.1:22000/data/ prefer = /data/
path = share ignore = Name {. *} repeat = 1800 backup = Name * backuploc =
central backupdir = / data / backup batch = true owner = false group = true
maxthreads = 4 rsync = false log = true logfile =
/var/log/unison/sync_data.log Tried to roll back to the old version, but
all the same ... Help please advice how to fix this problem?
--
Best regards, Maksim Kopachovets
Alan Schmitt alan.schmitt@polytechnique.org [unison-users]
2017-07-05 11:47:16 UTC
Permalink
"MKmkc[" == Maksim Kopachovets m ***@gmail com [unison-users] <unison-users-***@yahoogroups.com> writes:

MKmkc[> Good afternoon. After upgrading to version 2.48.4, when trying to
MKmkc[> synchronize produces an error: Fatal error: Server error files: error error
MKmkc[> 23 while adding a watcher The watcher can be disabled by setting preference
MKmkc[> 'watch' to false My configuration file:
MKmkc[> root = /data/ root = socket://192.168.2.1:22000/data/ prefer = /data/
MKmkc[> path = share ignore = Name {. *} repeat = 1800 backup = Name * backuploc =
MKmkc[> central backupdir = / data / backup batch = true owner = false group = true
MKmkc[> maxthreads = 4 rsync = false log = true logfile =
MKmkc[> /var/log/unison/sync_data.log Tried to roll back to the old version, but
MKmkc[> all the same ... Help please advice how to fix this problem?

Did you try setting
watch = false
in your configuration file?

Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
Maksim Kopachovets m.kopachovets@gmail.com [unison-users]
2017-07-05 11:55:10 UTC
Permalink
Yes, I tried to add this line, but got a new error
Fatal error: Server: File monitoring helper program not running
Post by Alan Schmitt ***@polytechnique.org [unison-users]
MKmkc[> Good afternoon. After upgrading to version 2.48.4, when trying to
MKmkc[> synchronize produces an error: Fatal error: Server error files: error error
MKmkc[> 23 while adding a watcher The watcher can be disabled by setting preference
MKmkc[> root = /data/ root = socket://192.168.2.1:22000/data/ prefer = /data/
MKmkc[> path = share ignore = Name {. *} repeat = 1800 backup = Name * backuploc =
MKmkc[> central backupdir = / data / backup batch = true owner = false group = true
MKmkc[> maxthreads = 4 rsync = false log = true logfile =
MKmkc[> /var/log/unison/sync_data.log Tried to roll back to the old version, but
MKmkc[> all the same ... Help please advice how to fix this problem?
Did you try setting
watch = false
in your configuration file?
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
Alan Schmitt alan.schmitt@polytechnique.org [unison-users]
2017-07-05 12:09:10 UTC
Permalink
"MK" == Maksim Kopachovets <***@gmail.com> writes:

MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running

This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.

Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
Maksim Kopachovets m.kopachovets@gmail.com [unison-users]
2017-07-05 12:13:16 UTC
Permalink
I noticed another strange thing. I have 4 folders on this server ...
Folder1 Folder2 Folder3 Folder4 If you enable synchronization 3 and 4
folders, then all ... if I include one or two, then the error flies ...
also does not help to include only the folder1 or folder2 immediately there
is an error ... It normally synchronizes only 3 and 4 folders .. Because of
what can be such a problem?
Post by Alan Schmitt ***@polytechnique.org [unison-users]
MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running
This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
'Benjamin C. Pierce' bcpierce@cis.upenn.edu [unison-users]
2017-07-05 13:16:43 UTC
Permalink
Running with

-debug verbose

may give a hint what is happening.

- B
Post by Maksim Kopachovets ***@gmail.com [unison-users]
I noticed another strange thing. I have 4 folders on this server ...
Folder1
Folder2
Folder3
Folder4
If you enable synchronization 3 and 4 folders, then all ... if I include one or two, then the error flies ... also does not help to include only the folder1 or folder2 immediately there is an error ... It normally synchronizes only 3 and 4 folders .. Because of what can be such a problem?
MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running
This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
Maksim Kopachovets m.kopachovets@gmail.com [unison-users]
2017-07-05 15:33:41 UTC
Permalink
Started with -debug verbose. Where unisond is running, an error has been
issued:

[server: fswatch+] >> ERROR
unexpected%20error%2023%20while%20adding%20a%20watcher
[server: remote+] Sending fatal exception (id: 9)
[server: remote+] send [rsp] '\132\149\166\190\000\000\000\138\000\000...'
158 bytes
[server: remote_emit+] dump:
\t\000\000\000b\161\000\000\000hrsp\132\149\166\190\000\000\000\138\000\000\000\000\000\000\000%\000\000\000\020\145\t\135Filesystem
watcher error: unexpected error 23 while adding a watcher\nThe watcher can
be disabled by setting preference 'watch' to false

but where the client is running continues to work, I will observe...
Post by 'Benjamin C. Pierce' ***@cis.upenn.edu [unison-users]
Running with
-debug verbose
may give a hint what is happening.
- B
I noticed another strange thing. I have 4 folders on this server ...
Folder1 Folder2 Folder3 Folder4 If you enable synchronization 3 and 4
folders, then all ... if I include one or two, then the error flies ...
also does not help to include only the folder1 or folder2 immediately there
is an error ... It normally synchronizes only 3 and 4 folders .. Because of
what can be such a problem?
Post by Alan Schmitt ***@polytechnique.org [unison-users]
MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running
This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
'Benjamin C. Pierce' bcpierce@cis.upenn.edu [unison-users]
2017-07-05 21:37:12 UTC
Permalink
There might also be some information at the beginning of the debug trace to suggest why it thinks it’s in “watch” mode (or at least to confirm that it does).

What does your whole config file look like?

- B
[server: fswatch+] >> ERROR unexpected%20error%2023%20while%20adding%20a%20watcher
[server: remote+] Sending fatal exception (id: 9)
[server: remote+] send [rsp] '\132\149\166\190\000\000\000\138\000\000...' 158 bytes
[server: remote_emit+] dump: \t\000\000\000b\161\000\000\000hrsp\132\149\166\190\000\000\000\138\000\000\000\000\000\000\000%\000\000\000\020\145\t\135Filesystem watcher error: unexpected error 23 while adding a watcher\nThe watcher can be disabled by setting preference 'watch' to false
but where the client is running continues to work, I will observe...
Running with
-debug verbose
may give a hint what is happening.
- B
Post by Maksim Kopachovets ***@gmail.com [unison-users]
I noticed another strange thing. I have 4 folders on this server ...
Folder1
Folder2
Folder3
Folder4
If you enable synchronization 3 and 4 folders, then all ... if I include one or two, then the error flies ... also does not help to include only the folder1 or folder2 immediately there is an error ... It normally synchronizes only 3 and 4 folders .. Because of what can be such a problem?
MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running
This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
Maksim Kopachovets m.kopachovets@gmail.com [unison-users]
2017-07-06 06:11:43 UTC
Permalink
Good afternoon.

My configuration file:

root = /data/
root = socket://192.168.2.1:22000//data/
prefer = /data/

path = share

ignore = Name {.*}
repeat = 1800

backup = Name *
backuploc = central
backupdir = /data/backup

batch = true
owner = false
group = true
maxthreads = 4
debug = verbose

log = true
logfile = /var/log/unison/sync_data.log



Once again I will describe how everything happens:

If you run in such a view as above, but without debug = verbose. The
following happens, it starts looking for files, and then gives an error:
Filesystem watcher error: unexpected error 23 while adding a watcher \ nThe
watcher can be disabled by setting preference 'watch' to false

I add the line watch = false to the configuration file, the same thing
happens, but the error is different:
Fatal error: Server: File monitoring helper program not running

As can be seen from the configuration file, the path for synchronization
looks like path = share, if it is changed to:
Path = share/folder1
Path = share/folder2
Path = share/folder3
Path = share/folder4
Will be the same, but if on:
# Path = share/folder1
# Path = share/folder2
Path = share/folder3
Path = share/folder4
That is, to comment the first 2 folders, the synchronization is successful,
if you add one more or two folders for synchronization, the error again
flies even if you leave only the first and second folders, and 3 and 4
comment ...

Can the problem be somewhere in these folders (the total size of the ball
is 110Tb)? I even tried to delete the archives, that he re-created them,
but nothing helped either ...
Post by 'Benjamin C. Pierce' ***@cis.upenn.edu [unison-users]
There might also be some information at the beginning of the debug trace
to suggest why it thinks it’s in “watch” mode (or at least to confirm that
it does).
What does your whole config file look like?
- B
[server: fswatch+] >> ERROR unexpected%20error%2023%
20while%20adding%20a%20watcher
[server: remote+] Sending fatal exception (id: 9)
[server: remote+] send [rsp] '\132\149\166\190\000\000\000\138\000\000...' 158 bytes
[server: remote_emit+] dump: \t\000\000\000b\161\000\000\
000hrsp\132\149\166\190\000\000\000\138\000\000\000\000\
unexpected error 23 while adding a watcher\nThe watcher can be disabled by
setting preference 'watch' to false
but where the client is running continues to work, I will observe...
Post by 'Benjamin C. Pierce' ***@cis.upenn.edu [unison-users]
Running with
-debug verbose
may give a hint what is happening.
- B
I noticed another strange thing. I have 4 folders on this server ...
Folder1 Folder2 Folder3 Folder4 If you enable synchronization 3 and 4
folders, then all ... if I include one or two, then the error flies ...
also does not help to include only the folder1 or folder2 immediately there
is an error ... It normally synchronizes only 3 and 4 folders .. Because of
what can be such a problem?
Post by Alan Schmitt ***@polytechnique.org [unison-users]
MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running
This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
Maksim Kopachovets m.kopachovets@gmail.com [unison-users]
2017-07-15 12:28:46 UTC
Permalink
So I could not overcome this mistake... But I noticed one regularity, if I
specify the synchronization path deeper, then everything is ok... But as
soon as you point to the level above, immediately the error... Maybe
somewhere it rests on some parameter?
Post by Maksim Kopachovets ***@gmail.com [unison-users]
Good afternoon.
root = /data/
root = socket://192.168.2.1:22000//data/
prefer = /data/
path = share
ignore = Name {.*}
repeat = 1800
backup = Name *
backuploc = central
backupdir = /data/backup
batch = true
owner = false
group = true
maxthreads = 4
debug = verbose
log = true
logfile = /var/log/unison/sync_data.log
If you run in such a view as above, but without debug = verbose. The
Filesystem watcher error: unexpected error 23 while adding a watcher \
nThe watcher can be disabled by setting preference 'watch' to false
I add the line watch = false to the configuration file, the same thing
Fatal error: Server: File monitoring helper program not running
As can be seen from the configuration file, the path for synchronization
Path = share/folder1
Path = share/folder2
Path = share/folder3
Path = share/folder4
# Path = share/folder1
# Path = share/folder2
Path = share/folder3
Path = share/folder4
That is, to comment the first 2 folders, the synchronization is
successful, if you add one more or two folders for synchronization, the
error again flies even if you leave only the first and second folders, and
3 and 4 comment ...
Can the problem be somewhere in these folders (the total size of the ball
is 110Tb)? I even tried to delete the archives, that he re-created them,
but nothing helped either ...
Post by 'Benjamin C. Pierce' ***@cis.upenn.edu [unison-users]
There might also be some information at the beginning of the debug trace
to suggest why it thinks it’s in “watch” mode (or at least to confirm that
it does).
What does your whole config file look like?
- B
[server: fswatch+] >> ERROR unexpected%20error%2023%20whil
e%20adding%20a%20watcher
[server: remote+] Sending fatal exception (id: 9)
[server: remote+] send [rsp] '\132\149\166\190\000\000\000\138\000\000...' 158 bytes
[server: remote_emit+] dump: \t\000\000\000b\161\000\000\00
0hrsp\132\149\166\190\000\000\000\138\000\000\000\000\000\
000\000%\000\000\000\020\145\t\135Filesystem watcher error: unexpected
error 23 while adding a watcher\nThe watcher can be disabled by setting
preference 'watch' to false
but where the client is running continues to work, I will observe...
Post by 'Benjamin C. Pierce' ***@cis.upenn.edu [unison-users]
Running with
-debug verbose
may give a hint what is happening.
- B
I noticed another strange thing. I have 4 folders on this server ...
Folder1 Folder2 Folder3 Folder4 If you enable synchronization 3 and 4
folders, then all ... if I include one or two, then the error flies ...
also does not help to include only the folder1 or folder2 immediately there
is an error ... It normally synchronizes only 3 and 4 folders .. Because of
what can be such a problem?
Post by Alan Schmitt ***@polytechnique.org [unison-users]
MK> Yes, I tried to add this line, but got a new error
MK> Fatal error: Server: File monitoring helper program not running
This is very strange, it's as if unison thought it was launched in
watching mode. I have no idea what could cause this.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-05: 409.65, 2016-05: 407.70
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
--
Best regards, Maksim Kopachovets
Continue reading on narkive:
Loading...