Anyone here using MX Linux as a server? [Solved]

[figueroa]

running a desktop-oriented linux distribution on a public-facing server is certainly contrary to BestPractices. Full stop.

No need to "Full stop." A lot of people run server functions on their desktop computers. The kernel refinement is more important to the desktop (responsiveness) than it is to the server. You can also install your server into a VirtualBox virtual machine if you'd like to segregate your stuff. No need to give the impression that MX is fatally flawed as a server.

[acecombat2]

I do, am using Mx19 as server. currently I'm using the systemd due to script and ready made setup like jellyfin in repos, plex server, vm workstation, dockers, samba, printer server, and nomachine.

I am using mxlinux as my platform for server due to mxtools that made life easy like disk management, gpart, snapshot, nvidia driver installation. which is essential to have quick emergency administration and re-setup. I'm used to desktop to manage server rather by terminal. Stable, no headache.

Reason I don't go pure debian, because is a pain without auto detect monitor correctly. both stretch and busters.

Waiting for the day that ZFS can be install without issues in MX 19.

Code: Select all

[code]
System:    Host: kkg8server-MX19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=53df2d21-b546-44c6-a9fb-6b224b889ab9 ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Z620 Workstation v: N/A 
           serial: <filter> Chassis: type: 6 serial: <filter> 
           Mobo: Hewlett-Packard model: 158A v: 0.00 serial: <filter> BIOS: Hewlett-Packard 
           v: J61 v03.69 date: 03/25/2014 
CPU:       Topology: 10-Core model: Intel Xeon E5-2660 v2 bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3E (62) stepping: 4 microcode: 42E L2 cache: 25.0 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 87788 
           Speed: 2195 MHz min/max: 1200/3000 MHz Core speeds (MHz): 1: 2195 2: 2195 3: 2195 
           4: 2195 5: 2195 6: 2195 7: 2195 8: 2195 9: 2196 10: 2195 11: 2196 12: 2195 13: 2195 
           14: 2195 15: 2195 16: 2195 17: 2195 18: 2196 19: 2195 20: 2196 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GK107GL [Quadro K2000] vendor: Hewlett-Packard driver: nvidia 
           v: 418.74 bus ID: 05:00.0 chip ID: 10de:0ffe 
           Display: x11 server: X.Org 1.20.4 driver: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1360x768~60Hz 
           OpenGL: renderer: Quadro K2000/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 direct render: Yes 
Audio:     Device-1: Intel C600/X79 series High Definition Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1d20 
           Device-2: NVIDIA GK107 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 05:00.1 chip ID: 10de:0e1b 
           Device-3: Barco Display Systems type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus ID: 4-1.1:3 chip ID: 0600:6416 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: 3.2.6-k port: f040 bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel 82574L Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: 3.2.6-k port: e000 bus ID: 01:00.0 chip ID: 8086:10d3 
           IF: eth1 state: down mac: <filter> 
           IF-ID-1: br-8497be340fe0 state: up speed: N/A duplex: N/A mac: <filter> 
           IF-ID-2: docker0 state: up speed: N/A duplex: N/A mac: <filter> 
           IF-ID-3: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
           IF-ID-4: veth0f8449e state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-5: veth40798c5 state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-6: veth694376f state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-7: vetha07a0d2 state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-8: vethb2f9fcc state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-9: vetheaa3b49 state: up speed: 10000 Mbps duplex: full mac: <filter> 
           IF-ID-10: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter> 
           IF-ID-11: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter> 
           IF-ID-12: wg0 state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 3.05 TiB used: 1.45 TiB (47.6%) 
           ID-1: /dev/nvme0n1 vendor: A-Data model: SX6000LNP size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: V9001c00 scheme: GPT 
           ID-2: /dev/sda vendor: Western Digital model: WD5000AAKX-00U6AA0 size: 465.76 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1H15 
           scheme: MBR 
           ID-3: /dev/sdb vendor: Western Digital model: WD10EZEX-00MFCA0 size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 1A01 scheme: GPT 
           ID-4: /dev/sdc vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB 
           block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 1A02 scheme: GPT 
           ID-5: /dev/sdd model: WISE 480GB size: 447.13 GiB block size: physical: 512 B 
           logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 3B0 scheme: MBR 
           ID-6: /dev/sde vendor: Kingston model: SA400S37120G size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: B1D1 scheme: GPT 
RAID:      Hardware-1: Intel C600/X79 series SATA RAID Controller driver: ahci v: 3.0 port: f020 
           bus ID: 00:1f.2 chip ID: 8086.2826 rev: 05 
Partition: ID-1: / raw size: 109.51 GiB size: 107.29 GiB (97.97%) used: 43.06 GiB (40.1%) 
           fs: ext4 dev: /dev/sde2 
           ID-2: swap-1 size: 2.03 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sde3 
Sensors:   System Temperatures: cpu: 49.0 C mobo: N/A gpu: nvidia temp: 42 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb [arch=amd64] https://download.docker.com/linux/debian buster stable
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/buster/ buster main
           Active apt repos in: /etc/apt/sources.list.d/atom.list 
           1: deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           Active apt repos in: /etc/apt/sources.list.d/jellyfin.list 
           1: deb [arch=amd64] https://repo.jellyfin.org/debian buster main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           Active apt repos in: /etc/apt/sources.list.d/nvidia-container-runtime.list 
           1: deb https://nvidia.github.io/libnvidia-container/debian10/$(ARCH) /
           2: deb https://nvidia.github.io/nvidia-container-runtime/debian10/$(ARCH) /
           Active apt repos in: /etc/apt/sources.list.d/plexmediaserver.list 
           1: deb https://downloads.plex.tv/repo/deb/ public main
           Active apt repos in: /etc/apt/sources.list.d/syncthing.list 
           1: deb https://apt.syncthing.net/ syncthing stable
           No active apt repos in: /etc/apt/sources.list.d/unstable-wireguard.list 
           Active apt repos in: /etc/apt/sources.list.d/various.list 
           1: deb http://download.virtualbox.org/virtualbox/debian buster contrib
Info:      Processes: 475 Uptime: 2d 7h 50m Memory: 31.34 GiB used: 3.82 GiB (12.2%) 
           Init: systemd v: 241 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash 
           v: 5.0.3 running in: quick-system-in inxi: 3.0.36 

Best Distro for beginners.

Prefer Gui Text editor like geany or atom or featherpad than using vim or nano.

[brianm]

I run a home server with MX19

Running:
Samba shares (8 separate drives)
Apache
PHP
MySQL (mariadb)
PHPmyadmin
CUPS (printing)
Calibre (ebooks)
DNS server (for ad and tracker blocking etc)

I use the web facilities as a development area for the various web sites I look after. The only trouble I had was when I upgraded from MX 18 to 19 as PHPmyadmin was not in the repository. I found it in the Debian test repo and I did request it to be added, I don't know if its been done yet.

I keep my home network from the internet via a Netgear Prosafe Firewall. My network is setup to use this DNS server as default so all devices are protected from trackers and ads.

I've never opened my server to the internet, I'm not sure I know enough about the appropriate security.

Let us know how you get on krauser...

Brian

[Sparky]

I use CentOS for my servers, it's easier to handle as it is server friendly from the start but a nightmare to use as a desktop OS.

[m_pav]

For a home server, you should be fine, but for a web facing server, I would be a little hesitant to use MX in its current form. Even as a home server, I'd be inclined to strip back some of the things I deem as unnecessary for server use.

[Route99]

I'm working on a data server using MX19.
Most of the test work I do in a VM (virtual machine).
I make and work with a clone of it as if I make a mistake I'm not sure to be able to repair... I trough away the cloned version, make a new clone and continue...

My current server is a Debian Jessie LTS. The AMD350 CPU-based mobo is from 2011, so I wanna test if MX-Buster-based will give me a lighter version than the original Debian-Buster-based.... The dataserver works through Webdav/https/port 443 and we have 2 of them, identical and on 2 locations.

The 1st impression: The basic setup of MX was very easy.
The coming time I need to understand the new webdav config setup/files as I've seen that is quite different from Debian Jessie.

I allways used a firewall since 2011, all ports closed except for webdav sharing.

But now... iptables is replaced by nftables, so have to learn that to.
And I consider to use fail2ban. If things get to unsure for our safety standard, we may consider to use Teamviewer, so all ports can be closed, as TV has another technique.

[bassplayer69]

...

Waiting for the day that ZFS can be install without issues in MX 19.

What issues are you having getting ZFS installed and working with MX-19?

[figueroa]

Truth telling, although I replied, above, that MX wasn't fatally flawed for server functions, I don't do it and wouldn't recommend it because it is against conventional wisdom for all the right reasons. In my original reply I was feeling warm and fuzzy, while thinking about server security is better done when feeling cold and prickly.

Much also depends on what one means by "server." A file server for your LAN isn't as exposed to unauthorized access as a public web server or mail server.

I always custom build a stripped-down version of the OS to do just the needed server functions. The two servers I do run currently, one local and one remote, are on Gentoo (which is difficult, but suits me), and in the past I've also used Debian (decently easy and practical) and Slackware (didn't really like). I try to make the server as hostile as possible to potential unauthorized access. In practice I lean towards paraniod -- lock everything down -- then open up to the minimum to accomplish the job(s) intended.

[acecombat2]

...

Waiting for the day that ZFS can be install without issues in MX 19.

What issues are you having getting ZFS installed and working with MX-19?

I'm kinda forgotten, I think is the dependency (dkms? or zfs-spl) issue could not install even following debian buster guide. I'm currently using linux raid via webmin. since I could not get it right on the go, I postponed it. I need to test it again to get accurate issue.

[acecombat2]

I'm working on a data server using MX19.
Most of the test work I do in a VM (virtual machine).
I make and work with a clone of it as if I make a mistake I'm not sure to be able to repair... I trough away the cloned version, make a new clone and continue...

My current server is a Debian Jessie LTS. The AMD350 CPU-based mobo is from 2011, so I wanna test if MX-Buster-based will give me a lighter version than the original Debian-Buster-based.... The dataserver works through Webdav/https/port 443 and we have 2 of them, identical and on 2 locations.

The 1st impression: The basic setup of MX was very easy.
The coming time I need to understand the new webdav config setup/files as I've seen that is quite different from Debian Jessie.

I allways used a firewall since 2011, all ports closed except for webdav sharing.

But now... iptables is replaced by nftables, so have to learn that to.
And I consider to use fail2ban. If things get to unsure for our safety standard, we may consider to use Teamviewer, so all ports can be closed, as TV has another technique.

I recommend nomachine to replace teamviewer.

and you can always rely on vpn application like wireguard and openvpn to access the server.