@Not_Oles said: I think (but I am not sure) my Chromebook is giving me hterm, into which I sometimes am pasting. The hterm will be connected via ssh to some remote shell, into which the paste goes. The remote shell often is running somebody else's highly variantly configured vi/vim. Occasionally I have seen sequences similar to ESC [ 200 ~ or ESC [ 201 ~. I will have to pay more attention next time this happens.
Make sure your TERM specifies something that's roughly the same as what your terminal program actually supports / sends (in this case, the bracketing is probably done by hterm).
@Not_Oles said: I think (but I am not sure) my Chromebook is giving me hterm, into which I sometimes am pasting. The hterm will be connected via ssh to some remote shell, into which the paste goes. The remote shell often is running somebody else's highly variantly configured vi/vim. Occasionally I have seen sequences similar to ESC [ 200 ~ or ESC [ 201 ~. I will have to pay more attention next time this happens.
Make sure your TERM specifies something that's roughly the same as what your terminal program actually supports / sends (in this case, the bracketing is probably done by hterm).
It only happens once every few months that I see a few "Esc [" characters. Mostly everything is okay. It's interesting. I'm assuming that these are just "non-printable" characters which somehow are visible in a corner case. Mostly everything works okay. So I haven't paid attention. Next time it happens, if it happens again, I will try to pay attention to the environment in which it happens. Thanks for your interest and for your kind comment, @ralf!
Reboot succeeded without a power reset. Does that mean the bug mentioned in the OP has been fixed?
root@sid ~ # w
01:04:11 up 1 day, 6:46, 1 user, load average: 0.61, 0.77, 0.83
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 187.189.238.1 01:02 1.00s 0.02s ? w
root@sid ~ # apt-get update
Get:1 http://deb.debian.org/debian sid InRelease [180 kB]
Get:2 http://deb.debian.org/debian sid/contrib Sources [55.4 kB]
Get:3 http://deb.debian.org/debian sid/main Sources [10.0 MB]
Get:4 http://deb.debian.org/debian sid/main amd64 Packages [9,428 kB]
Get:5 http://deb.debian.org/debian sid/main Translation-en [6,977 kB]
Get:6 http://deb.debian.org/debian sid/contrib amd64 Packages [59.1 kB]
Fetched 26.7 MB in 2s (13.3 MB/s)
Reading package lists... Done
root@sid ~ # apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
linux-image-amd64
The following packages will be upgraded:
curl gdb libcurl3-gnutls libcurl4 libnghttp2-14 qemu-system qemu-system-arm qemu-system-common
qemu-system-data qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc
qemu-system-x86 qemu-utils
15 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 100 MB of archives.
After this operation, 49.2 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian sid/main amd64 libnghttp2-14 amd64 1.52.0-1 [72.3 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 curl amd64 7.88.1-1 [313 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libcurl4 amd64 7.88.1-1 [385 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 gdb amd64 13.1-1 [3,818 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libcurl3-gnutls amd64 7.88.1-1 [379 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 qemu-system-arm amd64 1:7.2+dfsg-4 [8,978 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 qemu-system-x86 amd64 1:7.2+dfsg-4 [9,264 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 qemu-system-data all 1:7.2+dfsg-4 [1,276 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 qemu-system-sparc amd64 1:7.2+dfsg-4 [5,182 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 qemu-system-ppc amd64 1:7.2+dfsg-4 [7,507 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 qemu-system-misc amd64 1:7.2+dfsg-4 [46.2 MB]
Get:12 http://deb.debian.org/debian sid/main amd64 qemu-system-mips amd64 1:7.2+dfsg-4 [13.3 MB]
Get:13 http://deb.debian.org/debian sid/main amd64 qemu-system-common amd64 1:7.2+dfsg-4 [2,138 kB]
Get:14 http://deb.debian.org/debian sid/main amd64 qemu-utils amd64 1:7.2+dfsg-4 [1,281 kB]
Get:15 http://deb.debian.org/debian sid/main amd64 qemu-system amd64 1:7.2+dfsg-4 [31.5 kB]
Fetched 100 MB in 1s (105 MB/s)
(Reading database ... 53305 files and directories currently installed.)
Preparing to unpack .../00-libnghttp2-14_1.52.0-1_amd64.deb ...
Unpacking libnghttp2-14:amd64 (1.52.0-1) over (1.51.0-1) ...
Preparing to unpack .../01-curl_7.88.1-1_amd64.deb ...
Unpacking curl (7.88.1-1) over (7.87.0-2) ...
Preparing to unpack .../02-libcurl4_7.88.1-1_amd64.deb ...
Unpacking libcurl4:amd64 (7.88.1-1) over (7.87.0-2) ...
Preparing to unpack .../03-gdb_13.1-1_amd64.deb ...
Unpacking gdb (13.1-1) over (13.0.91.20230210-0.1) ...
Preparing to unpack .../04-libcurl3-gnutls_7.88.1-1_amd64.deb ...
Unpacking libcurl3-gnutls:amd64 (7.88.1-1) over (7.87.0-2) ...
Preparing to unpack .../05-qemu-system-arm_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-arm (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../06-qemu-system-x86_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-x86 (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../07-qemu-system-data_1%3a7.2+dfsg-4_all.deb ...
Unpacking qemu-system-data (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../08-qemu-system-sparc_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-sparc (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../09-qemu-system-ppc_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-ppc (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../10-qemu-system-misc_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-misc (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../11-qemu-system-mips_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-mips (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../12-qemu-system-common_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-common (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../13-qemu-utils_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-utils (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../14-qemu-system_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Setting up qemu-system-common (1:7.2+dfsg-4) ...
Setting up libnghttp2-14:amd64 (1.52.0-1) ...
Setting up libcurl3-gnutls:amd64 (7.88.1-1) ...
Setting up gdb (13.1-1) ...
Setting up qemu-system-data (1:7.2+dfsg-4) ...
Setting up qemu-system-arm (1:7.2+dfsg-4) ...
Setting up libcurl4:amd64 (7.88.1-1) ...
Setting up curl (7.88.1-1) ...
Setting up qemu-utils (1:7.2+dfsg-4) ...
Setting up qemu-system-mips (1:7.2+dfsg-4) ...
Setting up qemu-system-sparc (1:7.2+dfsg-4) ...
Setting up qemu-system-x86 (1:7.2+dfsg-4) ...
Setting up qemu-system-ppc (1:7.2+dfsg-4) ...
Setting up qemu-system-misc (1:7.2+dfsg-4) ...
Setting up qemu-system (1:7.2+dfsg-4) ...
Processing triggers for libc-bin (2.36-8) ...
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
root@sid ~ #
root@sid ~ # uname -r
6.1.0-4-amd64
root@sid ~ #
root@sid ~ # apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-image-6.1.0-5-amd64
The following packages will be upgraded:
linux-image-amd64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 76.4 MB of archives.
After this operation, 540 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian sid/main amd64 linux-image-6.1.0-5-amd64 amd64 6.1.12-1 [76.4 MB]
Get:2 http://deb.debian.org/debian sid/main amd64 linux-image-amd64 amd64 6.1.12-1 [1,480 B]
Fetched 76.4 MB in 1s (111 MB/s)
Selecting previously unselected package linux-image-6.1.0-5-amd64.
(Reading database ... 53305 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-5-amd64_6.1.12-1_amd64.deb ...
Unpacking linux-image-6.1.0-5-amd64 (6.1.12-1) ...
Preparing to unpack .../linux-image-amd64_6.1.12-1_amd64.deb ...
Unpacking linux-image-amd64 (6.1.12-1) over (6.1.11-1) ...
Setting up linux-image-6.1.0-5-amd64 (6.1.12-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-4-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-4-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-5-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-5-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-5-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-5-amd64
Found initrd image: /boot/initrd.img-6.1.0-5-amd64
Found linux image: /boot/vmlinuz-6.1.0-4-amd64
Found initrd image: /boot/initrd.img-6.1.0-4-amd64
Found linux image: /boot/vmlinuz-5.10.0-20-amd64
Found initrd image: /boot/initrd.img-5.10.0-20-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up linux-image-amd64 (6.1.12-1) ...
root@sid ~ # root@sid ~ # reboot
root@sid ~ # Connection to ex100.metalvps.com closed by remote host.
Connection to ex100.metalvps.com closed.
chronos@penguin:~$ sleep 70
chronos@penguin:~$ ping -c 2 ex100.metalvps.com
PING ex100.metalvps.com (65.109.119.181) 56(84) bytes of data.
64 bytes from ex100.metalvps.com (65.109.119.181): icmp_seq=1 ttl=52 time=187 ms
64 bytes from ex100.metalvps.com (65.109.119.181): icmp_seq=2 ttl=52 time=187 ms
--- ex100.metalvps.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 187.106/187.239/187.372/0.133 ms
chronos@penguin:~$ ssh e
Linux sid 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1 (2023-02-15) x86_64
Welcome to MetalVPS!
Last login: Wed Feb 22 01:13:19 2023 from 187.189.238.1
root@sid ~ #
~~~
@Not_Oles said: Feb 15 00:42:26 sid dbus-daemon[545]: [system] Unable to reload configuration: Failed to open "/usr/share/dbus-1/system.conf": No such file or directory
Previously, I wondered:
@Not_Oles said: Reboot succeeded without a power reset. Does that mean the bug mentioned in the OP has been fixed?
Here is /usr/share/dbus-1/system.conf:
root@sid ~ # ls -l /usr/share/dbus-1/system.conf
-rw-r--r-- 1 root root 5807 Feb 8 13:21 /usr/share/dbus-1/system.conf
root@sid ~ # cat -n $_
1 <!-- This configuration file controls the systemwide message bus.
2 Add a system-local.conf and edit that rather than changing this
3 file directly. -->
4
5 <!-- Note that there are any number of ways you can hose yourself
6 security-wise by screwing up this file; in particular, you
7 probably don't want to listen on any more addresses, add any more
8 auth mechanisms, run as a different user, etc. -->
9
10 <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
11 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
12 <busconfig>
13
14 <!-- Our well-known bus type, do not change this -->
15 <type>system</type>
16
17 <!-- Run as special user -->
18 <user>messagebus</user>
19
20 <!-- Fork into daemon mode -->
21 <fork/>
22
23 <!-- We use system service launching using a helper -->
24 <standard_system_servicedirs/>
25
26 <!-- This is a setuid helper that is used to launch system services -->
27 <servicehelper>/usr/lib/dbus-1.0/dbus-daemon-launch-helper</servicehelper>
28
29 <!-- Write a pid file -->
30 <pidfile>/run/dbus/pid</pidfile>
31
32 <!-- Enable logging to syslog -->
33 <syslog/>
34
35 <!-- Only allow socket-credentials-based authentication -->
36 <auth>EXTERNAL</auth>
37
38 <!-- Only listen on a local socket. (abstract=/path/to/socket
39 means use abstract namespace, don't really create filesystem
40 file; only Linux supports this. Use path=/whatever on other
41 systems.) -->
42 <listen>unix:path=/run/dbus/system_bus_socket</listen>
43
44 <policy context="default">
45 <!-- All users can connect to system bus -->
46 <allow user="*"/>
47
48 <!-- Holes must be punched in service configuration files for
49 name ownership and sending method calls -->
50 <deny own="*"/>
51 <deny send_type="method_call"/>
52
53 <!-- Signals and reply messages (method returns, errors) are allowed
54 by default -->
55 <allow send_type="signal"/>
56 <allow send_requested_reply="true" send_type="method_return"/>
57 <allow send_requested_reply="true" send_type="error"/>
58
59 <!-- All messages may be received by default -->
60 <allow receive_type="method_call"/>
61 <allow receive_type="method_return"/>
62 <allow receive_type="error"/>
63 <allow receive_type="signal"/>
64
65 <!-- Allow anyone to talk to the message bus -->
66 <allow send_destination="org.freedesktop.DBus"
67 send_interface="org.freedesktop.DBus" />
68 <allow send_destination="org.freedesktop.DBus"
69 send_interface="org.freedesktop.DBus.Introspectable"/>
70 <allow send_destination="org.freedesktop.DBus"
71 send_interface="org.freedesktop.DBus.Properties"/>
72 <allow send_destination="org.freedesktop.DBus"
73 send_interface="org.freedesktop.DBus.Containers1"/>
74 <!-- But disallow some specific bus services -->
75 <deny send_destination="org.freedesktop.DBus"
76 send_interface="org.freedesktop.DBus"
77 send_member="UpdateActivationEnvironment"/>
78 <deny send_destination="org.freedesktop.DBus"
79 send_interface="org.freedesktop.DBus.Debug.Stats"/>
80 <deny send_destination="org.freedesktop.DBus"
81 send_interface="org.freedesktop.systemd1.Activator"/>
82 </policy>
83
84 <!-- Only systemd, which runs as root, may report activation failures. -->
85 <policy user="root">
86 <allow send_destination="org.freedesktop.DBus"
87 send_interface="org.freedesktop.systemd1.Activator"/>
88 </policy>
89
90 <!-- root may monitor the system bus. -->
91 <policy user="root">
92 <allow send_destination="org.freedesktop.DBus"
93 send_interface="org.freedesktop.DBus.Monitoring"/>
94 </policy>
95
96 <!-- If the Stats interface was enabled at compile-time, root may use it.
97 Copy this into system.local.conf or system.d/*.conf if you want to
98 enable other privileged users to view statistics and debug info -->
99 <policy user="root">
100 <allow send_destination="org.freedesktop.DBus"
101 send_interface="org.freedesktop.DBus.Debug.Stats"/>
102 </policy>
103
104 <!-- Include legacy configuration location -->
105 <include ignore_missing="yes">/etc/dbus-1/system.conf</include>
106
107 <!-- The defaults for these limits are hard-coded in dbus-daemon.
108 Some clarifications:
109 Times are in milliseconds (ms); 1000ms = 1 second
110 133169152 bytes = 127 MiB
111 33554432 bytes = 32 MiB
112 150000ms = 2.5 minutes -->
113 <!-- <limit name="max_incoming_bytes">133169152</limit> -->
114 <!-- <limit name="max_incoming_unix_fds">64</limit> -->
115 <!-- <limit name="max_outgoing_bytes">133169152</limit> -->
116 <!-- <limit name="max_outgoing_unix_fds">64</limit> -->
117 <!-- <limit name="max_message_size">33554432</limit> -->
118 <!-- <limit name="max_message_unix_fds">16</limit> -->
119 <!-- <limit name="service_start_timeout">25000</limit> -->
120 <!-- <limit name="auth_timeout">5000</limit> -->
121 <!-- <limit name="pending_fd_timeout">150000</limit> -->
122 <!-- <limit name="max_completed_connections">2048</limit> -->
123 <!-- <limit name="max_incomplete_connections">64</limit> -->
124 <!-- <limit name="max_connections_per_user">256</limit> -->
125 <!-- <limit name="max_pending_service_starts">512</limit> -->
126 <!-- <limit name="max_names_per_connection">512</limit> -->
127 <!-- <limit name="max_match_rules_per_connection">512</limit> -->
128 <!-- <limit name="max_replies_per_connection">128</limit> -->
129
130 <!-- Config files are placed here that among other things, punch
131 holes in the above policy for specific services. -->
132 <includedir>system.d</includedir>
133
134 <includedir>/etc/dbus-1/system.d</includedir>
135
136 <!-- This is included last so local configuration can override what's
137 in this standard file -->
138 <include ignore_missing="yes">/etc/dbus-1/system-local.conf</include>
139
140 <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>
141
142 </busconfig>
root@sid ~ #
So, does the presence of /usr/share/dbus-1/system.conf together with the fact that the most recent reboot succeeded mean that the bug reported in the OP might be fixed?
@Not_Oles I have been occupied with some work stuff this week. I plan to start using this account starting next week. Hope thats OK. What I'll do is still in the works, yet. Thanks again.
@typicalGta said:
Would love to try it out, Could I get an account?
I got an SHA key tho, Does that work for you?
Hi @typicalGta! Thanks for asking! Your Provider tag makes it seem like you already have very adequate facilities. Could you please help me understand what you want to do on the server and why? Thanks again! Tom
@typicalGta said:
Would love to try it out, Could I get an account?
I got an SHA key tho, Does that work for you?
Hi @typicalGta! Thanks for asking! Your Provider tag makes it seem like you already have very adequate facilities. Could you please help me understand what you want to do on the server and why? Thanks again! Tom
Hello,
As I mentioned, Would like to try it out, Never rly got to understand how these shared shells worked so some experience would help in the long run for me. If you only have limited slots then let me know, wouldn't wanna take the opportunity from someone who needs it.
@typicalGta said:
Would love to try it out, Could I get an account?
I got an SHA key tho, Does that work for you?
Hi @typicalGta! Thanks for asking! Your Provider tag makes it seem like you already have very adequate facilities. Could you please help me understand what you want to do on the server and why? Thanks again! Tom
Hello,
As I mentioned, Would like to try it out, Never rly got to understand how these shared shells worked so some experience would help in the long run for me. If you only have limited slots then let me know, wouldn't wanna take the opportunity from someone who needs it.
Hi @typicalGta! Please continue your contributions to the community here at LES and please also consider more specifically what you might want to do on the server. Then, in a while, please ask again for an account. Best wishes! Tom
@arifur said: @Not_Oles I have not done anything with the account yet. I hope that's okay.
Sure, definitely okay. It's been a pleasure talking with you here and by email. I hope we remain friends for a long time.
By the way, I'm thinking of installing a web server. My default goto would be Apache. If you have a reason to want a different web server, I would appreciate it if you would tell me which one and why. Additionally, I suppose we could install Laravel, though I've not tried it and don't know hardly anything about it.
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 2126
Multi Core | 15227
Full Test | https://browser.geekbench.com/v5/cpu/20618088
When you log in to your account, you could run the w command to see who is logged in and also the load averages.
If not too many people seem to be trying to run things, maybe you could exercise quite a few of the cores?
so maybe you could try using nice(1) sometime? I haven't used nice(1) for a while. I don't know how well nice(1) integrates with multi-threaded commands. Do you know?
I made you an account. Please try logging in with something like:
Please reread all the warnings in the OP. Please make sure to keep backups! Please let me know about all the stuff that isn't working.
Please monitor and please contribute some great content here in this thread! If you never post about what you are doing on the server, people might imagine that you are not using your account and no longer need it! 🤔
Rethinking my above posted reply to your question, maybe I have not given a sufficiently clear answer. That's because it's a shared server, so we have to be sensitive to what our neighbors are doing. For a short period of time, if you want to run something huge, and not too many others are around, then please go ahead! If you want to run something huge and for a long period of time, maybe post about it here in the thread before you go ahead?
Guys, apologies, there still is a bunch of stuff which needs to be installed. For example, Go and ndpresponder. Probably, in addition to Go and ndpresponder, there still remain more configuration steps with LXC. I need to carefully review what we did on the other server, make some notes, adjust for Alpine host --> Debian host, and try to finish up the configuration here. Everything will be fixed eventually. Please speak up as you notice things which need to be done.
@Not_Oles said:
Sure, definitely okay. It's been a pleasure talking with you here and by email. I hope we remain friends for a long time.
Thank you. And definitely.
By the way, I'm thinking of installing a web server. My default goto would be Apache. If you have a reason to want a different web server, I would appreciate it if you would tell me which one and why. Additionally, I suppose we could install Laravel, though I've not tried it and don't know hardly anything about it.
Apache is fine. As for laravel there is no need, it wont be wise to keep a "dev mode" laravel in "open" internet.
Following today's apt-get update, upgrade, and reboot, there are also new /etc/subuid and new /etc/subgid LXC configuration files which you can see.
Your starting subuid from /etc/subuid and your starting subgid from /etc/subgid should match the starting subuid and the starting subgid in your ~/.config/lxc/default.conf. So a change to your ~/.config/lxc/default.conf should be needed.
Please let me know about any issues by posting here in the thread.
@Not_Oles said: If you have time, could you please post the commands you ran to create the container? Thanks!
subenhon@sid:~$ #make sure the correct idmap is in the conf file
subenhon@sid:~$ cat $HOME/.config/lxc/default.conf
lxc.include = /etc/lxc/default.conf
lxc.idmap = u 0 165536 65536
lxc.idmap = g 0 165536 65536
subenhon@sid:~$ #create ubuntu container
subenhon@sid:~$ lxc-create -n ubuntu -f $HOME/.config/lxc/default.conf -t download -- --dist ubuntu --release focal --arch amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu focal amd64 (20230215_07:43) container.
To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
subenhon@sid:~$ # avoid apparmor error
subenhon@sid:~$ echo -e "lxc.apparmor.profile = unconfined\nlxc.apparmor.allow_nesting = 0\n" >> $HOME/.local/share/lxc/ubuntu/config
subenhon@sid:~$ #add x access to home before start the container or some error occurs
subenhon@sid:~$ chmod +x $HOME
subenhon@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu
subenhon@sid:~$ #attach and set the password
subenhon@sid:~$ systemd-run --unit=my-attach --user --scope -p "Delegate=yes" -- lxc-attach -n ubuntu
Running scope as unit: my-attach.scope
root@ubuntu:/# passwd
New password:
Retype new password:
passwd: password updated successfully
root@ubuntu:/# exit
exit
subenhon@sid:~$ # restart and login with the password
subenhon@sid:~$ lxc-stop -n ubuntu
subenhon@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu -F
Ubuntu 20.04.5 LTS ubuntu console
ubuntu login: root
Password:
Welcome to Ubuntu 20.04.5 LTS (GNU/Linux 6.1.0-4-amd64 x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted byapplicable law.
root@ubuntu:~#
My recent several days have been invested in reading about configuring LXC, trying multiple different LXC configurations, and seeing multiple different and fascinating errors! I managed to follow @subenhon's steps, except that I didn't use the -F foreground option on restart. The result seems to be a working Ubuntu container with IPv4 but no IPv6 yet.
In order to get LXC really going on bare Debian, one needs at least a little understanding of LXC itself, cgroups, apparmor, systemd, networking, command line, the Debian package system and more. But, if I can (almost, sort of) do it with help from @subenhon, you certainly can do it too!
chronos@penguin:~/servers/hetzner/new2$ ssh [email protected] -p 42365
Linux sid 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1 (2023-02-15) x86_64
Welcome to MetalVPS!
Last login: Thu Mar 2 16:29:17 2023 from 187.189.238.1
notoles@sid:~$ cat $HOME/.config/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
lxc.idmap = u 0 100000 65536
lxc.idmap = g 0 100000 65536
notoles@sid:~$ cat /etc/sub*id
notoles:100000:65536
subenhon:200000:65536
notoles:100000:65536
subenhon:200000:65536
notoles@sid:~$ lxc-create -n ubuntu -f $HOME/.config/lxc/default.conf -t download -- --dist ubuntu --release focal --arch amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu focal amd64 (20230228_07:44) container.
To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
notoles@sid:~$ grep apparmor $HOME/.local/share/lxc/ubuntu/config
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
notoles@sid:~$ echo -e "lxc.apparmor.profile = unconfined\nlxc.apparmor.allow_nesting = 0\n" >> $HOME/.local/share/lxc/ubuntu/config
notoles@sid:~$ grep apparmor $HOME/.local/share/lxc/ubuntu/config
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
lxc.apparmor.profile = unconfined
lxc.apparmor.allow_nesting = 0
notoles@sid:~$ # chmod +x $HOME
notoles@sid:~$ ls -l .. | grep notoles
drwx--x--x 6 notoles notoles 4096 Mar 2 01:18 notoles
notoles@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu
Running scope as unit: my-unit.scope
notoles@sid:~$ # Attach and set the password
notoles@sid:~$ systemd-run --unit=my-attach --user --scope -p "Delegate=yes" -- lxc-attach -n ubuntu
Running scope as unit: my-attach.scope
root@ubuntu:/# passwd
New password:
Retype new password:
passwd: password updated successfully
root@ubuntu:/# exit
exit
notoles@sid:~$ # restart and login with the password
notoles@sid:~$ lxc-stop -n ubuntu
notoles@sid:~$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start -n ubuntu
Running scope as unit: my-unit.scope
notoles@sid:~$ systemd-run --unit=my-attach --user --scope -p "Delegate=yes" -- lxc-attach -n ubuntu
Running scope as unit: my-attach.scope
root@ubuntu:/# ping -c 2 google.com
PING google.com (216.58.207.238) 56(84) bytes of data.
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=1 ttl=118 time=6.54 ms
64 bytes from arn09s19-in-f14.1e100.net (216.58.207.238): icmp_seq=2 ttl=118 time=6.67 ms
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 6.540/6.603/6.666/0.063 ms
root@ubuntu:/# ping6 -c 2 google.com
ping6: connect: Network is unreachable
root@ubuntu:/#
@Not_Oles said: Please think of your MetalVPS account as ephemeral! It might blow up! We or you might reinstall the Node! 🤦♂️
Hello!
I might wipe and reinstall this server. Maybe as soon as tomorrow. 😱 Does anyone who already has an account need anything on it? Does anyone who already has an account need temporary accommodations elsewhere? Thanks!
Somehow an EX101 suddenly appeared in my Hetzner Robot control panel! 💥 So this EX100 is scheduled for cancellation on April 4, 2023. 😢
Today is March 27 and March has 31 days. Sounds like that's what's left of today, plus March 28, 29, 30, and 31, plus April 1, 2, 3, and 4 that this EX100 can be used. Counting today, that's 9 days.
Does anybody want the entire server either for the 9 days or else as a transfer into their Hetzner account? I might be willing to reinstall it (again) for you or to give you access to Hetzner installimage so you could do the install yourself if you wish.
I probably want $30.33, but maybe not, depending on who / whatever. 🤩
Comments
Make sure your TERM specifies something that's roughly the same as what your terminal program actually supports / sends (in this case, the bracketing is probably done by hterm).
@Not_Oles can i have one pie?
thanks
ThemeForest Profile
It only happens once every few months that I see a few "Esc [" characters. Mostly everything is okay. It's interesting. I'm assuming that these are just "non-printable" characters which somehow are visible in a corner case. Mostly everything works okay. So I haven't paid attention. Next time it happens, if it happens again, I will try to pay attention to the environment in which it happens. Thanks for your interest and for your kind comment, @ralf!
MetalVPS
Hi @seenu!
Here you go: 🍰
Thanks for the bump!
Best wishes!
Tom
MetalVPS
Am I too late? 😭
Teehee!
All of the pies are half eaten.
🥧🍰
Webhosting24 aff best VPS; ServerFactory aff best VDS; Cloudie best ASN; Huel aff best brotein.
Hello!
Kernel update:
MetalVPS
Qemu-KVM and Linux kernel updates
Reboot succeeded without a power reset. Does that mean the bug mentioned in the OP has been fixed?
root@sid ~ # w
01:04:11 up 1 day, 6:46, 1 user, load average: 0.61, 0.77, 0.83
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 187.189.238.1 01:02 1.00s 0.02s ? w
root@sid ~ # apt-get update
Get:1 http://deb.debian.org/debian sid InRelease [180 kB]
Get:2 http://deb.debian.org/debian sid/contrib Sources [55.4 kB]
Get:3 http://deb.debian.org/debian sid/main Sources [10.0 MB]
Get:4 http://deb.debian.org/debian sid/main amd64 Packages [9,428 kB]
Get:5 http://deb.debian.org/debian sid/main Translation-en [6,977 kB]
Get:6 http://deb.debian.org/debian sid/contrib amd64 Packages [59.1 kB]
Fetched 26.7 MB in 2s (13.3 MB/s)
Reading package lists... Done
root@sid ~ # apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
linux-image-amd64
The following packages will be upgraded:
curl gdb libcurl3-gnutls libcurl4 libnghttp2-14 qemu-system qemu-system-arm qemu-system-common
qemu-system-data qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc
qemu-system-x86 qemu-utils
15 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 100 MB of archives.
After this operation, 49.2 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian sid/main amd64 libnghttp2-14 amd64 1.52.0-1 [72.3 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 curl amd64 7.88.1-1 [313 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libcurl4 amd64 7.88.1-1 [385 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 gdb amd64 13.1-1 [3,818 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libcurl3-gnutls amd64 7.88.1-1 [379 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 qemu-system-arm amd64 1:7.2+dfsg-4 [8,978 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 qemu-system-x86 amd64 1:7.2+dfsg-4 [9,264 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 qemu-system-data all 1:7.2+dfsg-4 [1,276 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 qemu-system-sparc amd64 1:7.2+dfsg-4 [5,182 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 qemu-system-ppc amd64 1:7.2+dfsg-4 [7,507 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 qemu-system-misc amd64 1:7.2+dfsg-4 [46.2 MB]
Get:12 http://deb.debian.org/debian sid/main amd64 qemu-system-mips amd64 1:7.2+dfsg-4 [13.3 MB]
Get:13 http://deb.debian.org/debian sid/main amd64 qemu-system-common amd64 1:7.2+dfsg-4 [2,138 kB]
Get:14 http://deb.debian.org/debian sid/main amd64 qemu-utils amd64 1:7.2+dfsg-4 [1,281 kB]
Get:15 http://deb.debian.org/debian sid/main amd64 qemu-system amd64 1:7.2+dfsg-4 [31.5 kB]
Fetched 100 MB in 1s (105 MB/s)
(Reading database ... 53305 files and directories currently installed.)
Preparing to unpack .../00-libnghttp2-14_1.52.0-1_amd64.deb ...
Unpacking libnghttp2-14:amd64 (1.52.0-1) over (1.51.0-1) ...
Preparing to unpack .../01-curl_7.88.1-1_amd64.deb ...
Unpacking curl (7.88.1-1) over (7.87.0-2) ...
Preparing to unpack .../02-libcurl4_7.88.1-1_amd64.deb ...
Unpacking libcurl4:amd64 (7.88.1-1) over (7.87.0-2) ...
Preparing to unpack .../03-gdb_13.1-1_amd64.deb ...
Unpacking gdb (13.1-1) over (13.0.91.20230210-0.1) ...
Preparing to unpack .../04-libcurl3-gnutls_7.88.1-1_amd64.deb ...
Unpacking libcurl3-gnutls:amd64 (7.88.1-1) over (7.87.0-2) ...
Preparing to unpack .../05-qemu-system-arm_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-arm (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../06-qemu-system-x86_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-x86 (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../07-qemu-system-data_1%3a7.2+dfsg-4_all.deb ...
Unpacking qemu-system-data (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../08-qemu-system-sparc_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-sparc (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../09-qemu-system-ppc_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-ppc (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../10-qemu-system-misc_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-misc (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../11-qemu-system-mips_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-mips (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../12-qemu-system-common_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system-common (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../13-qemu-utils_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-utils (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Preparing to unpack .../14-qemu-system_1%3a7.2+dfsg-4_amd64.deb ...
Unpacking qemu-system (1:7.2+dfsg-4) over (1:7.2+dfsg-3) ...
Setting up qemu-system-common (1:7.2+dfsg-4) ...
Setting up libnghttp2-14:amd64 (1.52.0-1) ...
Setting up libcurl3-gnutls:amd64 (7.88.1-1) ...
Setting up gdb (13.1-1) ...
Setting up qemu-system-data (1:7.2+dfsg-4) ...
Setting up qemu-system-arm (1:7.2+dfsg-4) ...
Setting up libcurl4:amd64 (7.88.1-1) ...
Setting up curl (7.88.1-1) ...
Setting up qemu-utils (1:7.2+dfsg-4) ...
Setting up qemu-system-mips (1:7.2+dfsg-4) ...
Setting up qemu-system-sparc (1:7.2+dfsg-4) ...
Setting up qemu-system-x86 (1:7.2+dfsg-4) ...
Setting up qemu-system-ppc (1:7.2+dfsg-4) ...
Setting up qemu-system-misc (1:7.2+dfsg-4) ...
Setting up qemu-system (1:7.2+dfsg-4) ...
Processing triggers for libc-bin (2.36-8) ...
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
root@sid ~ #
root@sid ~ # uname -r
6.1.0-4-amd64
root@sid ~ #
root@sid ~ # apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-image-6.1.0-5-amd64
The following packages will be upgraded:
linux-image-amd64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 76.4 MB of archives.
After this operation, 540 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian sid/main amd64 linux-image-6.1.0-5-amd64 amd64 6.1.12-1 [76.4 MB]
Get:2 http://deb.debian.org/debian sid/main amd64 linux-image-amd64 amd64 6.1.12-1 [1,480 B]
Fetched 76.4 MB in 1s (111 MB/s)
Selecting previously unselected package linux-image-6.1.0-5-amd64.
(Reading database ... 53305 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-5-amd64_6.1.12-1_amd64.deb ...
Unpacking linux-image-6.1.0-5-amd64 (6.1.12-1) ...
Preparing to unpack .../linux-image-amd64_6.1.12-1_amd64.deb ...
Unpacking linux-image-amd64 (6.1.12-1) over (6.1.11-1) ...
Setting up linux-image-6.1.0-5-amd64 (6.1.12-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-4-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-4-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-5-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-5-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-5-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-5-amd64
Found initrd image: /boot/initrd.img-6.1.0-5-amd64
Found linux image: /boot/vmlinuz-6.1.0-4-amd64
Found initrd image: /boot/initrd.img-6.1.0-4-amd64
Found linux image: /boot/vmlinuz-5.10.0-20-amd64
Found initrd image: /boot/initrd.img-5.10.0-20-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up linux-image-amd64 (6.1.12-1) ...
root@sid ~ # root@sid ~ # reboot
root@sid ~ # Connection to ex100.metalvps.com closed by remote host.
Connection to ex100.metalvps.com closed.
chronos@penguin:~$ sleep 70
chronos@penguin:~$ ping -c 2 ex100.metalvps.com
PING ex100.metalvps.com (65.109.119.181) 56(84) bytes of data.
64 bytes from ex100.metalvps.com (65.109.119.181): icmp_seq=1 ttl=52 time=187 ms
64 bytes from ex100.metalvps.com (65.109.119.181): icmp_seq=2 ttl=52 time=187 ms
--- ex100.metalvps.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 187.106/187.239/187.372/0.133 ms
chronos@penguin:~$ ssh e
Linux sid 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1 (2023-02-15) x86_64
Welcome to MetalVPS!
Last login: Wed Feb 22 01:13:19 2023 from 187.189.238.1
root@sid ~ #
~~~
MetalVPS
MetalVPS
Is The Bug Fixed?
Here's a line from the Bug Report in the OP:
Previously, I wondered:
Here is /usr/share/dbus-1/system.conf:
So, does the presence of /usr/share/dbus-1/system.conf together with the fact that the most recent reboot succeeded mean that the bug reported in the OP might be fixed?
@arifur @jcolideles @localhost @subenhon Want to post about what you are doing on the server? If/when you have time, no rush.
Does anyone else want an account?
Friendly greetings!
MetalVPS
@Not_Oles I have been occupied with some work stuff this week. I plan to start using this account starting next week. Hope thats OK. What I'll do is still in the works, yet. Thanks again.
Hi @localhost! Thanks for your report! Best wishes!
MetalVPS
Would love to try it out, Could I get an account?
I got an SHA key tho, Does that work for you?
Hi @typicalGta! Thanks for asking! Your Provider tag makes it seem like you already have very adequate facilities. Could you please help me understand what you want to do on the server and why? Thanks again! Tom
MetalVPS
Hi @Nubuki!
I just now saw your post from 4 days ago! Sorry for the delay!
No, you are not too late. I could make you an account. But what about transcoding? Nothing illegal? No copyright violations?
Best!
Tom
MetalVPS
Hello,
As I mentioned, Would like to try it out, Never rly got to understand how these shared shells worked so some experience would help in the long run for me. If you only have limited slots then let me know, wouldn't wanna take the opportunity from someone who needs it.
@Not_Oles I have not done anything with the account yet. I hope that's okay.
Hi @typicalGta! Please continue your contributions to the community here at LES and please also consider more specifically what you might want to do on the server. Then, in a while, please ask again for an account. Best wishes! Tom
MetalVPS
Sure, definitely okay. It's been a pleasure talking with you here and by email. I hope we remain friends for a long time.
By the way, I'm thinking of installing a web server. My default goto would be Apache. If you have a reason to want a different web server, I would appreciate it if you would tell me which one and why. Additionally, I suppose we could install Laravel, though I've not tried it and don't know hardly anything about it.
MetalVPS
Thanks
nothing illegal but say how much CPU could I play with ?
Teehee!
Well,
nprocsaysThis thread's yabs says
and
When you log in to your account, you could run the
wcommand to see who is logged in and also the load averages.If not too many people seem to be trying to run things, maybe you could exercise quite a few of the cores?
Also, I just checked, and the server has
so maybe you could try using nice(1) sometime? I haven't used nice(1) for a while. I don't know how well nice(1) integrates with multi-threaded commands. Do you know?
I made you an account. Please try logging in with something like:
Please reread all the warnings in the OP. Please make sure to keep backups! Please let me know about all the stuff that isn't working.
Please monitor and please contribute some great content here in this thread! If you never post about what you are doing on the server, people might imagine that you are not using your account and no longer need it! 🤔
Have fun! 🎉
Best wishes!
Tom
MetalVPS
Rethinking my above posted reply to your question, maybe I have not given a sufficiently clear answer. That's because it's a shared server, so we have to be sensitive to what our neighbors are doing. For a short period of time, if you want to run something huge, and not too many others are around, then please go ahead! If you want to run something huge and for a long period of time, maybe post about it here in the thread before you go ahead?
Is this answer a better answer?
Friendly greetings!
MetalVPS
Guys, apologies, there still is a bunch of stuff which needs to be installed. For example, Go and ndpresponder. Probably, in addition to Go and ndpresponder, there still remain more configuration steps with LXC. I need to carefully review what we did on the other server, make some notes, adjust for Alpine host --> Debian host, and try to finish up the configuration here. Everything will be fixed eventually. Please speak up as you notice things which need to be done.
MetalVPS
Thank you. And definitely.
Apache is fine. As for laravel there is no need, it wont be wise to keep a "dev mode" laravel in "open" internet.
Hello!
Following today's apt-get update, upgrade, and reboot, there are also new /etc/subuid and new /etc/subgid LXC configuration files which you can see.
Your starting subuid from /etc/subuid and your starting subgid from /etc/subgid should match the starting subuid and the starting subgid in your ~/.config/lxc/default.conf. So a change to your ~/.config/lxc/default.conf should be needed.
Please let me know about any issues by posting here in the thread.
Best!
Tom
MetalVPS
@subenhon said:
My recent several days have been invested in reading about configuring LXC, trying multiple different LXC configurations, and seeing multiple different and fascinating errors!
I managed to follow @subenhon's steps, except that I didn't use the -F foreground option on restart. The result seems to be a working Ubuntu container with IPv4 but no IPv6 yet.
In order to get LXC really going on bare Debian, one needs at least a little understanding of LXC itself, cgroups, apparmor, systemd, networking, command line, the Debian package system and more. But, if I can (almost, sort of) do it with help from @subenhon, you certainly can do it too!
MetalVPS
Hello!
I might wipe and reinstall this server. Maybe as soon as tomorrow. 😱 Does anyone who already has an account need anything on it? Does anyone who already has an account need temporary accommodations elsewhere? Thanks!
Best!
Tom
MetalVPS
Hello!
Somehow an EX101 suddenly appeared in my Hetzner Robot control panel! 💥 So this EX100 is scheduled for cancellation on April 4, 2023. 😢
Today is March 27 and March has 31 days. Sounds like that's what's left of today, plus March 28, 29, 30, and 31, plus April 1, 2, 3, and 4 that this EX100 can be used. Counting today, that's 9 days.
Does anybody want the entire server either for the 9 days or else as a transfer into their Hetzner account? I might be willing to reinstall it (again) for you or to give you access to Hetzner installimage so you could do the install yourself if you wish.
I probably want $30.33, but maybe not, depending on who / whatever. 🤩
Friendly greetings!
Tom
MetalVPS