docker-timemachine: [Big Sur Beta 7] There was an error configuring “/Volumes/***” as a Time Machine backup disk.
Hi there!
Thanks for this really cool project! I have it working really well on one of my machines 😃
However, on my other machine (Which is actually running the Big Sur beta) I am unable to get this to work. I get the following error message after going to time machine, choosing the correct share for my user, and entering the details correctly:
There was an error configuring “/Volumes/***” as a Time Machine backup disk.
*** is a substitution for the actual shares name
On my Catalina machine, it works really well. It connected no worries, and it’s currently creating its first backup now 😃
I wouldn’t really know where to start debugging this, so this is where I am asking for a bit of help, here are some logs from the container itself, they perhaps point towards a problem?:
timemachine | ===============================================================
timemachine | INTERNAL ERROR: Signal 11 in pid 58 (4.12.2)
timemachine | If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
timemachine | ===============================================================
timemachine | PANIC (pid 58): internal error
timemachine | unable to produce a stack trace on this platform
timemachine | dumping core in /var/log/samba/cores/smbd
timemachine | ===============================================================
timemachine | INTERNAL ERROR: Signal 11 in pid 67 (4.12.2)
timemachine | If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
timemachine | ===============================================================
timemachine | PANIC (pid 67): internal error
timemachine | unable to produce a stack trace on this platform
timemachine | dumping core in /var/log/samba/cores/smbd
timemachine | ===============================================================
timemachine | INTERNAL ERROR: Signal 11 in pid 87 (4.12.2)
timemachine | If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
timemachine | ===============================================================
timemachine | PANIC (pid 87): internal error
timemachine | unable to produce a stack trace on this platform
timemachine | dumping core in /var/log/samba/cores/smbd
timemachine | Failed to fetch record!
timemachine | pcap cache not loaded
timemachine | ===============================================================
timemachine | INTERNAL ERROR: Signal 11 in pid 94 (4.12.2)
timemachine | If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
timemachine | ===============================================================
timemachine | PANIC (pid 94): internal error
timemachine | unable to produce a stack trace on this platform
timemachine | dumping core in /var/log/samba/cores/smbd
timemachine | smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 3 (sequence id 3) (granted = 1, low = 2, range = 1)
timemachine | ===============================================================
timemachine | INTERNAL ERROR: Signal 11 in pid 110 (4.12.2)
timemachine | If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
timemachine | ===============================================================
timemachine | PANIC (pid 110): internal error
timemachine | unable to produce a stack trace on this platform
timemachine | dumping core in /var/log/samba/cores/smbd
timemachine | ===============================================================
timemachine | INTERNAL ERROR: Signal 11 in pid 118 (4.12.2)
timemachine | If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
timemachine | ===============================================================
timemachine | PANIC (pid 118): internal error
timemachine | unable to produce a stack trace on this platform
timemachine | dumping core in /var/log/samba/cores/smbd
And in case it is needed: My docker-compose.yaml
file:
version: "2.1"
services:
time-machine:
image: mbentley/timemachine:smb-armv7l
container_name: timemachine
network_mode: host
environment:
- SHARE_NAME=TimeMachine
- EXTERNAL_CONF=/conf
volumes:
- /home/jacob/Time-Machine/users:/conf
- /home/jacob/Time-Machine/timemachine/var-lib-samba:/var/lib/samba
- /home/jacob/Time-Machine/timemachine/var-cache-samba:/var/cache/samba
- /home/jacob/Time-Machine/timemachine/run-samba:/run/samba
- /mnt/cache/Time-Machine/*:/opt/*
- /mnt/cache/Time-Machine/*:/opt/*
The .conf
file for the specific user:
TM_USERNAME=*
TM_GROUPNAME=*group
PASSWORD=***
SHARE_NAME=*s-timemachine
VOLUME_SIZE_LIMIT="300 G"
TM_UID=1000
TM_GID=1000
A few substitutions for the names, I have checked and made sure everything is right
I am not too familiar with Samba and with how Time Machine specifically works, so perhaps someone would be able to point me in the right direction? Happy to do any debugging steps or provide any logs 😃
I appreciate the help! And cheers for the great project!
EDIT: Nice, after all my redactions still forgot something 😛
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (7 by maintainers)
I wanted to circle back. I just upgraded to Big Sur now that it is GA and Time Machine backups seem to be working as far as I can tell but please reopen if you have any issues.
Well this certainly makes me glad I didn’t just jump right in with the Big Sur beta 😃
👍 ; would be curious if removing the max size on the share changes what Time Machine sees.
Thanks for the report. I can reproduce this as well as my time machine backups stopped happening 2 days ago; checked the logs and there it is. I’ll have to see if I can find something, either with the version of Alpine, Samba, or something of that nature. I haven’t seen this error before so it’s definitely something new.