Does any one successfully setup syncthing on AXT-1800?

bring.fringe18 · 2024-01-26T23:01:19.754Z

2024-01-26 11:57:24: Failed to create folder root directory mkdir /Snes saves: permission denied

You do not have Synching configured properly. You need to understand how mounted drives appear as directories. You need to read & adapt the configuration file I posted some 30+ posts ago.

OpenWrt uses the /etc/ & /etc/config for system wide configuration. OpenWrt does not include manual pages (man) to save space. See the attached video:

root@slateax:~# tree / -L 1
/
├── bin
├── dev
├── etc
├── init
├── lib
├── mnt
├── overlay
├── proc
├── rom
├── root
├── sbin
├── sys
├── tmp
├── usr
├── var -> tmp
└── www

Sir_SwampThing · 2024-01-26T23:14:44.136Z

I’m not sure which part I have configured wrong then?
I followed your config file and changed all instances of "/mnt/sda1/syncthing " to "/mount/mmcblk0/syncthing ".


config syncthing 'syncthing'
	option enabled '1'

	option gui_address 'http://0.0.0.0:8384'

	# Use internal flash for evaluation purpouses. Use external storage
	#   for production.
	# This filesystem must either support ownership/attributes or
	#   be readable/writable by the user specified in
	#   'option user'.
	# Consult syslog if things go wrong.
	option home '/mnt/mmcblk0/syncthing'

	# Changes to "niceness"/macprocs are not picked up by "reload_config"
	#   nor by "restart": the service has to be stopped/started
	#   for those to take effect
	option nice '10'

	# 0 to match the number of CPUs (default)
	# >0 to explicitly specify concurrency
	option macprocs '0'

	# Running as 'root' is possible, but not recommended
	option user 'syncthing'

bring.fringe18 · 2024-01-27T00:11:48.103Z

This conf looks correct. Did you ~~chmod~~ chown the /mnt/mmcblk0/syncthing dir over to the Syncthing ‘user’?

Sir_SwampThing · 2024-01-27T02:54:12.973Z

root@GL-AXT1800:/mnt/mmcblk0# cat /etc/config/syncthing
config syncthing 'syncthing'
        option enabled '1'
        option gui_address 'http://0.0.0.0:8384'
        # Use internal flash for evaluation purpouses. Use external storage
        #   for production.
        # This filesystem must either support ownership/attributes or
        #   be readable/writable by the user specified in
        #   'option user'.
        # Consult syslog if things go wrong.
        option home '/mnt/mmcblk0/syncthing'
        # Changes to "niceness"/macprocs are not picked up by "reload_config"
        #   nor by "restart": the service has to be stopped/started
        #   for those to take effect
        option nice '10'
        # 0 to match the number of CPUs (default)
        # >0 to explicitly specify concurrency
        option macprocs '0'
        # Running as 'root' is possible, but not recommended
        option user 'syncthing'

root@GL-AXT1800:/mnt/mmcblk0# chmod -R syncthing:syncthing /mnt/mmcblk0/syncthing
chmod: invalid mode 'syncthing:syncthing'
root@GL-AXT1800:/mnt/mmcblk0#

bring.fringe18 · 2024-01-27T05:29:20.554Z

That’s on me. I keep forgetting you’re not using a Linux filesystem on that storage device so chmod doesn’t apply here.

In your case I’d put a # in front of the option user 'syncthing' line in that conf, then check your paths in Syncthing GUI → Settings → Actions → Default Configuration → [ Edit Folder Defaults ] . You’ll need to restart Syncthing (Syncthing GUI → Actions → Restart).

There’s also a log in Syncthing that may be helpful for info under Actions.

Sir_SwampThing · 2024-01-27T11:29:48.904Z

It’s formatted as ext4, is that wrong?

admon · 2024-01-27T11:48:56.551Z

It might be just me, but chmod isn’t for user and groups, is it?
Try to run chown -R syncthing:syncthing /mnt/mmcblk0/syncthing instead.

Sir_SwampThing · 2024-01-27T12:00:36.000Z

And what result should I look for if I then use

ls -l

?

admon · 2024-01-27T12:03:35.523Z

should be syncthing & syncthing as user and group.
If everything fails you can still use

chmod 777 -Rv /mnt/mmcblk0/syncthing for any:any permission.

Sir_SwampThing · 2024-01-27T12:08:07.227Z

root@GL-AXT1800:/mnt/mmcblk0# ls -l
drwx------    4 syncthin syncthin      4096 Jan 26 21:29 syncthing

something like this?

admon · 2024-01-27T12:25:51.384Z

Yup, should be fine.

Sir_SwampThing · 2024-01-27T12:32:46.832Z

Unfortunately, same thing happening.

2024-01-27 12:31:31: Failed to create folder root directory mkdir /HX99G Syncthing: permission denied

2024-01-27 12:31:31: Error on folder "HX99G Syncthing" (l4ee6-zz9gu): folder path missing

admon · 2024-01-27T12:35:40.912Z

I don’t know much about syncthing but your folder is wrong.
Wherever you entered “/HX99G Syncthing” it must be /mnt/mmcblk0/syncthing

Sir_SwampThing · 2024-01-27T12:49:40.305Z

That’s just the label I have given to the saves folder on the Batocera machine.
The folder path is the correct path.
I believe (probably wrongly) that once I have created this it will be introduced to the router and the router should create a similar folder in /mnt/mmcblk0.

admon · 2024-01-27T12:51:13.195Z

Sir_SwampThing:

folder root directory mkdir /HX99G Syncthing

Pretty sure it’s not only a label.
mkdir /xxxx would try to create it on the router on the root-level, where it does not have permissions.

Sir_SwampThing · 2024-01-27T12:57:34.751Z

Screenshot_20240127_125608_Chrome759×774 75.3 KB

Sir_SwampThing · 2024-01-27T13:03:17.908Z

But looking at the Batocera files, I now realise I am definitely doing something wrong.
I thought I was creating a link to the userdata/share/saves/snes folder but clearly I am not, it’s just creating a folder in userdata called HX99G Syncthing.

I have now tried calling the folder Syncthing, no joy.
Tried working from the router to the Batocera machine, no joy.

Every attempt results in the same error message.

root@GL-AXT1800:/mnt/mmcblk0/syncthing# ls -l
-rw-r--r--    1 syncthin syncthin       794 Jan 27 14:49 cert.pem
-rw-------    1 syncthin syncthin      7901 Jan 27 15:27 config.xml
-rw-------    1 syncthin syncthin      7274 Jan 27 14:49 config.xml.v0
-rw-------    1 syncthin syncthin        33 Jan 27 14:51 csrftokens.txt
-rw-r--r--    1 syncthin syncthin       798 Jan 27 14:50 https-cert.pem
-rw-------    1 syncthin syncthin       288 Jan 27 14:50 https-key.pem
drwxr-xr-x    2 syncthin syncthin      4096 Jan 27 15:38 index-v0.14.0.db
-rw-------    1 syncthin syncthin       288 Jan 27 14:49 key.pem

root@GL-AXT1800:/mnt/mmcblk0/syncthing# cd syncthing
-ash: cd: can't cd to syncthing: No such file or directory
root@GL-AXT1800:/mnt/mmcblk0/syncthing# cd /mnt/mmcblk0/syncthing
root@GL-AXT1800:/mnt/mmcblk0/syncthing# ls -l
-rw-r--r--    1 syncthin syncthin       794 Jan 27 14:49 cert.pem
-rw-------    1 syncthin syncthin      7901 Jan 27 15:27 config.xml
-rw-------    1 syncthin syncthin      7274 Jan 27 14:49 config.xml.v0
-rw-------    1 syncthin syncthin        33 Jan 27 14:51 csrftokens.txt
-rw-r--r--    1 syncthin syncthin       798 Jan 27 14:50 https-cert.pem
-rw-------    1 syncthin syncthin       288 Jan 27 14:50 https-key.pem
drwxr-xr-x    2 syncthin syncthin      4096 Jan 27 15:38 index-v0.14.0.db
-rw-------    1 syncthin syncthin       288 Jan 27 14:49 key.pem
root@GL-AXT1800:/mnt/mmcblk0/syncthing# whoami
root

ls -l is reporting that Syncthing is the user.
whoami reports as root.
Is that because whoami is referring to the device as opposed to the /mnt/mmcblk0?

Sir_SwampThing · 2024-01-27T16:56:51.541Z

It appears that

/mnt/mmcblk0/syncthing

is owned(?) by Syncthing. But any folders created inside the syncthing directory/folder are still root root.

Is this correct?

admon · 2024-01-27T17:00:21.669Z

Sir_SwampThing:

But any folders created inside the syncthing directory/folder are still root root.

Is this correct?

Only if you create them. If syncthing creates them, they should be not root:root

Sir_SwampThing · 2024-01-27T17:18:24.444Z

OK, so I have

device = root root
mnt/mmcblk0 = root root… I believe these are both correct?

I have

mnt/mmcblk0/syncthing = syncthing syncthing… which I also believe is correct?

So I need to figure out why, when Syncthing tries to create a new directory inside the existing syncthing directory, it gets denied permission.