[Touch-packages] [Bug 1994810] Re: rsync 3.2.3 to module broken with read-only system error
** Description changed: There is a issue rsyncing to a rsync module with the error: failed: Read-only file system (30) Both server are ubuntu 22.04.1 with rsync version 3.2.3-8ubuntu3 I tried with no success "use chroot" different value options Permissions are OK in the end side Installing manually rsync package version 3.1.3-8ubuntu0.4 from ubuntu 20 in the end side server solves the issue (without any configuration changes) Also, a workaround (both same version of rsync), is to use the following parameters in rsync: -e ssh however, this might not work for automated cron scripts. 1) Start side server command: rsync -rptoglav /tmp/test/ ::test 2) End side server configuration of rsyncd.conf: === [test] - path = /tmp/test - read only = false - uid = root - gid = root + path = /etc/letsencrypt + read only = false + uid = root + gid = root === -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1994810 Title: rsync 3.2.3 to module broken with read-only system error Status in rsync package in Ubuntu: New Bug description: There is a issue rsyncing to a rsync module with the error: failed: Read-only file system (30) Both server are ubuntu 22.04.1 with rsync version 3.2.3-8ubuntu3 I tried with no success "use chroot" different value options Permissions are OK in the end side Installing manually rsync package version 3.1.3-8ubuntu0.4 from ubuntu 20 in the end side server solves the issue (without any configuration changes) Also, a workaround (both same version of rsync), is to use the following parameters in rsync: -e ssh however, this might not work for automated cron scripts. 1) Start side server command: rsync -rptoglav /tmp/test/ ::test 2) End side server configuration of rsyncd.conf: === [test] path = /etc/letsencrypt read only = false uid = root gid = root === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1994810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1994810] [NEW] rsync 3.2.3 to module broken with read-only system error
Public bug reported: There is a issue rsyncing to a rsync module with the error: failed: Read-only file system (30) Both server are ubuntu 22.04.1 with rsync version 3.2.3-8ubuntu3 I tried with no success "use chroot" different value options Permissions are OK in the end side Installing manually rsync package version 3.1.3-8ubuntu0.4 from ubuntu 20 in the end side server solves the issue (without any configuration changes) Also, a workaround (both same version of rsync), is to use the following parameters in rsync: -e ssh however, this might not work for automated cron scripts. 1) Start side server command: rsync -rptoglav /tmp/test/ ::test 2) End side server configuration of rsyncd.conf: === [test] path = /tmp/test read only = false uid = root gid = root === ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1994810 Title: rsync 3.2.3 to module broken with read-only system error Status in rsync package in Ubuntu: New Bug description: There is a issue rsyncing to a rsync module with the error: failed: Read-only file system (30) Both server are ubuntu 22.04.1 with rsync version 3.2.3-8ubuntu3 I tried with no success "use chroot" different value options Permissions are OK in the end side Installing manually rsync package version 3.1.3-8ubuntu0.4 from ubuntu 20 in the end side server solves the issue (without any configuration changes) Also, a workaround (both same version of rsync), is to use the following parameters in rsync: -e ssh however, this might not work for automated cron scripts. 1) Start side server command: rsync -rptoglav /tmp/test/ ::test 2) End side server configuration of rsyncd.conf: === [test] path = /tmp/test read only = false uid = root gid = root === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1994810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930482] Re: netplan crash on ubuntu 20.04 disabling network
Hi Nick,
I cannot longer reproduce this. This was about 1 year ago in a VPS in
OVH that we no longer have.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930482
Title:
netplan crash on ubuntu 20.04 disabling network
Status in netplan:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Incomplete
Bug description:
On ubuntu 20.04 with netplan 0.102-0ubuntu1~20.04.2, the server loss
both IPv4 and IPv6 address in a while with DHCP config. The are no way
to restore network, only by rebooting the server.
Trying to restart the server networking using "systemctl restart
systemd-networkd" or "netplan apply" fails.
Note: systemctl and netplay apply fails also with a netplan with
static IP address
The server runs on OVS in cloud.ramnode.com
I'm pasting config, logs, netplan and restart output (IP and mac
address are masked)
I don't see a workaound yet, only to restart server to change the
network configuration.
File: 50-cloud-init.yaml
==
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
accept-ra: true
dhcp4: true
dhcp6: true
match:
macaddress: **:**:**:**:**:**:**
mtu: 1500
set-name: ens3
=
Syslog
=
2021-06-01T19:31:01.063935-04:00 server systemd[1]: Stopped Network Service.
2021-06-01T19:31:01.066766-04:00 server systemd[1]: Starting Network
Service...
2021-06-01T19:31:01.161797-04:00 server systemd-networkd[2302]:
/run/systemd/network/10-netplan-ens3.network: MTUBytes= in [Link] section and
UseMTU= in [DHCP] section are set. Disabling UseMTU=.
2021-06-01T19:31:01.161990-04:00 server systemd-networkd[2302]: loop3456:
netdev ready
2021-06-01T19:31:01.162073-04:00 server systemd-networkd[2302]: Tunnel127:
Gained IPv6LL
2021-06-01T19:31:01.162184-04:00 server systemd-networkd[2302]: Tunnel126:
Gained IPv6LL
2021-06-01T19:31:01.162275-04:00 server systemd-networkd[2302]: loop3456:
Gained IPv6LL
2021-06-01T19:31:01.162349-04:00 server systemd-networkd[2302]: ens3: Gained
IPv6LL
2021-06-01T19:31:01.164685-04:00 server systemd-networkd[2302]: Assertion
'ifindex' failed at src/network/networkd-link.c:757, function link_get().
Aborting.
2021-06-01T19:31:01.553611-04:00 server systemd[1]: systemd-networkd.service:
Main process exited, code=dumped, status=6/ABRT
2021-06-01T19:31:01.553796-04:00 server systemd[1]: systemd-networkd.service:
Failed with result 'core-dump'.
2021-06-01T19:31:01.553892-04:00 server systemd[1]: Failed to start Network
Service.
2021-06-01T19:31:01.553983-04:00 server systemd[1]: systemd-networkd.service:
Scheduled restart job, restart counter is at 2.
output of: netapply --debug try
DEBUG:ens3 not found in {}
DEBUG:loop3456 not found in {}
DEBUG:Merged config:
network:
bridges:
loop3456:
accept-ra: false
addresses:
- 10.65.0.3/32
dhcp4: false
dhcp6: false
interfaces: []
ethernets:
ens3:
accept-ra: true
addresses:
- XXX.XXX.XXX.XXX/24
dhcp4: false
dhcp6: true
gateway4: XXX.XXX.XXX.XXX
match:
macaddress: **:**:**:**:**:**:**
mtu: 1500
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
search:
- uc.edu.ve
set-name: ens3
version: 2
DEBUG:New interfaces: set()
** (generate:1484): DEBUG: 20:14:22.895: Processing input file
/etc/netplan/50-static.yaml..
** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
** (generate:1484): DEBUG: 20:14:22.895: Processing input file
/etc/netplan/99-local.yaml..
** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
** (generate:1484): DEBUG: 20:14:22.895: We have some netdefs, pass them
through a final round of validation
** (generate:1484): DEBUG: 20:14:22.895: ens3: setting default backend to 1
** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
** (generate:1484): DEBUG: 20:14:22.895: loop3456: setting default backend to
1
** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
** (generate:1484): DEBUG: 20:14:22.896: Generating output files..
** (generate:1484):
