All Questions(server)

I could really use some help figuring out how to safely expand the root partition on my Linux server VM. I’ve added 50GB of extra space to the VM’s virtual disk, and I can see it using fdisk, but I'm unsure how to allocate it without breaking the system.

Here’s my current partition layout:

home-srv-01:~ #  lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    0  100G  0 disk 
├─sda1   8:1    0    8M  0 part 
├─sda2   8:2    0 30.8G  0 part /var
│                               /usr/local
│                               /tmp
│                               /boot/grub2/i386-pc
│                               /boot/grub2/x86_64-efi
│                               /opt
│                               /srv
│                               /.snapshots
│                               /root
│                               /
├─sda3   8:3    0 17.2G  0 part /home
└─sda4   8:4    0    2G  0 part [SWAP]
sr0     11:0    1 15.3G  0 rom  
home-srv-01:~ #

home-srv-01:~ # fdisk -l
GPT PMBR size mismatch (104857599 != 209715199) will be corrected by write.
Disk /dev/sda: 100 GiB, 107374182400 bytes, 209715200 sectors
Disk model: VMware Virtual S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A1C8759F-D45C-4FB4-A365-1402AD4516B3

Device         Start       End  Sectors  Size Type
/dev/sda1       2048     18431    16384    8M BIOS boot
/dev/sda2      18432  64600063 64581632 30.8G Linux filesystem
/dev/sda3   64600064 100661247 36061184 17.2G Linux filesystem
/dev/sda4  100661248 104857566  4196319    2G Linux swap
home-srv-01:~ # 

The goal is to expand the Btrfs root partition (sda2) into the new free space without losing the data on /home (sda3 XFS) or causing the system to become unbootable. Unfortunately, my earlier attempts resulted in boot issues, so I’m being extra cautious now.

Recap of Steps:

1. Backed up all data from /home (/dev/sda3).
2. Booted into a live CD/USB environment.
3. Moved data from /home to an external disk.
4. Ran swapoff /dev/sda4 and deleted /dev/sda4.
5. Deleted /dev/sda3 (this creates free space next to /dev/sda2).
6. Resized the Btrfs filesystem on /dev/sda2 using btrfs filesystem resize max /.
7. Recreated /dev/sda3 and restored the /home data from the backup.
8. Recreated /dev/sda4 and ran swapon /dev/sda4.
9. Once completed, the system does not boot anymore.

Thanks a lot in advance for any advice or step-by-step suggestions. I’d really appreciate your guidance.

LX

On Ubuntu 22.04.1 (AMD 3970x, 64GB RAM (memtest86 pass), several free TB on root filesystem, no SMART errors), I installed community mongodb with the standard directions here. Upon starting mongod in systemd, it failed with the journalctl -xe messages-

Apr 01 22:55:52 ganymede systemd[1]: Started MongoDB Database Server.
░░ Subject: A start job for unit mongod.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit mongod.service has finished successfully.
░░ 
░░ The job identifier is 9623.
Apr 01 22:55:52 ganymede sudo[427395]: pam_unix(sudo:session): session closed for user root
Apr 01 22:55:52 ganymede mongod[427399]: {"t":{"$date":"2025-04-02T05:55:52.613Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagem>
Apr 01 22:55:52 ganymede systemd[1]: mongod.service: Main process exited, code=exited, status=14/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit mongod.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 14.
Apr 01 22:55:52 ganymede systemd[1]: mongod.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit mongod.service has entered the 'failed' state with result 'exit-code'.

More specific error messages from the same start attempt appeared in /var/log/mongodb/mongod.log-

{"t":{"$date":"2025-04-01T22:55:52.617-07:00"},"s":"I",  "c":"CONTROL",  "id":20698,   "ctx":"main","msg":"***** SERVER RESTARTED *****"}
{"t":{"$date":"2025-04-01T22:55:52.620-07:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2025-04-01T22:55:52.620-07:00"},"s":"I",  "c":"CONTROL",  "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2025-04-01T22:55:52.621-07:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set at least one of the related parameters","attr":{"relatedParameters":["tcpFastOpenServer","tcpFastOpenClient","tcpFastOpenQueueSize"]}}
{"t":{"$date":"2025-04-01T22:55:52.621-07:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":25},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":25},"outgoing":{"minWireVersion":6,"maxWireVersion":25},"isInternalClient":true}}}
{"t":{"$date":"2025-04-01T22:55:52.632-07:00"},"s":"F",  "c":"ASSERT",   "id":23095,   "ctx":"main","msg":"Fatal assertion","attr":{"msgid":40475,"error":"FailedToParse: failed to parse time zone file for time zone identifier \"Asia/Riyadh87\": The version used in this timezone identifier is unsupported","file":"src/mongo/db/query/datetime/date_time_support.cpp","line":219}}
{"t":{"$date":"2025-04-01T22:55:52.632-07:00"},"s":"F",  "c":"ASSERT",   "id":23096,   "ctx":"main","msg":"\n\n***aborting after fassert() failure\n\n"}

That seems to indicate a problem with the package tzdata, so I checked it a few ways-

• dpkg --verify tzdata # no errors or output
• Checking the apt logs, zgrep -i tzdata /var/log/apt/*.gz, there was an update yesterday (31 Mar 2025)
• Checking the Riyadh tzdata files, find /usr/share/zoneinfo|grep "Riyadh"|xargs -n 1 zdump -v there were no error messages, though a few records had 'NULL' in them, but unclear if that indicates a problem.

So, I uninstalled that version (apt remove mongodb-org-server mongodb-org-shell mongodb-org-tools mongodb-org-mongos mongodb-org-database mongodb-org-database-tools-extra mongodb-mongosh mongodb-database-tools)

Then I installed previous versions from the community edition archive page by downloading .deb files, iterating through 8.0.5, 8.0.4, 8.0.3, 8.0.1 and 8.0.0. Installed each one by one, started it, checked if it failed -all failed- all with with the same "FailedToParse: failed to parse time zone file for time zone identifier "Asia/Riyadh87"" message in /var/log/mongodb/mongod.log.

This could be a "me problem," but it seems unlikely that a timezone file in tzdata with an unsupported format could get into Ubuntu's repository, and not affect any other services, and not get patched right away. However, I have run into tzdata issues previously on Ubuntu 22.04, and was able to resolve it with an apt reinstall.

I prefer to run services on bare metal, hence my efforts, so if anyone has some input, I'm grateful. For now I'll fire up mongodb on Docker and grit my teeth.

Update- Installing mongodb-server-org adds a default /etc/mongod.conf, which contains-

processManagement:
  timeZoneInfo: /usr/local/share/tzdb

I tried starting with and without those lines, no difference, mongod still scans Ubuntu's built-in tzdb and fails the assertion.

So I downloaded tzdb and untarred it to /usr/local/share/mytzdb, pointed mongod.conf to that location, and started mongod -no joy, fails the same way.

Maybe there's an env var that overrides? For now I'm running under Docker, no issues.

Oh- this morning an Ubuntu update had a tzdb refresh, lol. Didn't fix mongod tho.

Firstly, I'm not using IPv6 on my server, and IPv6 is being disabled.

However, if I run firewall-cmd --list-all-policies, I can see there's a default policy called allow-host-ipv6.

What does it actually do? I'm also have no idea where does this policy come from. I'm pretty sure that the /etc/firewalld/policies/ directory is empty. How can I get rid of it?

# firewall-cmd --list-all-policies
allow-host-ipv6 (active)
  priority: -15000
  target: CONTINUE
  ingress-zones: ANY
  egress-zones: HOST
  services: 
  ports: 
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
        rule family="ipv6" icmp-type name="neighbour-advertisement" accept
        rule family="ipv6" icmp-type name="neighbour-solicitation" accept
        rule family="ipv6" icmp-type name="router-advertisement" accept
        rule family="ipv6" icmp-type name="redirect" accept

The situation: Debian12 host, apache2 httpd serving git CGI (located in /repos/git) for cloning repos. Repos are stored in /repos directory, and are owned by git user to enable ssh access to them (e.g. to be able to write git push [email protected]:repos/repo.git in the console).

The issue is, upon running git clone https://example.com/repos.git when everything is owned by git user, git CGI prints this to stderr:

(13)Permission denied: [client <ip>:<port>] AH00035: access to /repos.git/info/refs denied (filesystem path '/repos/git') because search permissions are missing on a component of the path

and the clone commands works fine if i run chown -R www-data:www-data /repos. But this way, I can not access repo via ssh (fatal: detected dubious ownership in repository at /repos/repo.git on the client, even when git user is inside www-data group)

I tried making the directory owned by use git and group www-data and enabling sharedRepository=0640 in config (i also tried different values), but then the CGI script fails with this dubious ownership error. I tried setting up global config, I tried making directory 2777 and 0666 permissions, but nothing works.

To clarify I really don't like logging in as www-data user for ssh access to git repos. And I feel there must be something with sharedRepository that I can perform, but I can't wrap my head around what it should be.

P.S.: I do not need gitweb since I am running cgit, and apache2 config should (at least in theory) be irrelevant here.

I am trying to disable Jenins on this server,cause we do not need it anymore

ps -feww | grep jenkins

shows

jenkins     6646    6089  0 08:53 ?        00:00:00 npm start
jenkins     9180    6646 29 08:53 ?        01:19:15 next-server (v14.2.5)
jenkins    15769   12444  0 08:53 ?        00:00:02 /shared/argocd-dex rundex
jumicha      587438  544583  0 13:18 pts/0    00:00:00 grep --color=auto jenkins

What should be the next step? How to find out what started jenkins?

ps -p 9180 -o pid,vsz=MEMORY -o user,group=GROUP -o comm,args=ARGS
    PID MEMORY USER     GROUP    COMMAND         ARGS
   9180 21735356 jenkins 65533   next-server (v1 next-server (v14.2.5)

What was the thing that started next-server?

pstree -pn 9180
next-server (v1(9180)─┬─{next-server (v1}(9189)
                      ├─{next-server (v1}(9190)
                      ├─{next-server (v1}(9191)
                      ├─{next-server (v1}(9192)
                      ├─{next-server (v1}(9193)
                      ├─{next-server (v1}(9214)
                      ├─{next-server (v1}(12061)
                      ├─{next-server (v1}(12062)
                      ├─{next-server (v1}(12063)
                      └─{next-server (v1}(12064)