Posts

This is a quick note on how I got the Xen Orchestra Appliance (XOA) on a new XCP-ng server. I know there are many guides out there, and in fact this is not my original content, but I want to capture what I did to get it working. Here are the steps I performed on my server in order to install XOA: [14:16 xcpng ~]# bash -c "$(curl -sS http://xoa.io/deploy)" Welcome to the XOA auto-deploy script! Network settings: IP address? [dhcp] Your XOA will be started using DHCP xoa SSH account: Password? (disabled if empty) xoa account is disabled, to enable it later see https://xen-orchestra.com/docs/troubleshooting.html#set-or-recover-xoa-vm-password Importing XOA VM... Booting XOA VM... Waiting for your XOA to be ready… Your XOA is ready at https://192.168.1.207/ Default UI credentials: admin@admin.net/admin VM UUID: 19e56589-ed0d-5a24-c845-75b40b344f3b [14:24 xcpng ~]# Next, login to the XOA at https://192.168.1.207 using the default credential to connect the XCP-ng server this: ...

Like the title says, when restoring a Postgresql database onto a different server which happens to have a dfferent role owner, extra care is needed, otherwise similar error message below will come up: pg_restore: from TOC entry 217; 1259 17163 TABLE users_collections webdev1 pg_restore: error: could not execute query: ERROR: role "webdev1" does not exist Command was: ALTER TABLE public.users_collections OWNER TO webdev1; pg_restore: from TOC entry 218; 1259 17168 TABLE users_organizations webdev1 pg_restore: error: could not execute query: ERROR: role "webdev1" does not exist Command was: ALTER TABLE public.users_organizations OWNER TO webdev1; pg_restore: warning: errors ignored on restore: 19 What happened was that there was no role named webdev1 on the Postgreseql server where the database restoring was performed. Instead, on my database server, I had a role named webdev2. ...

On my main workstation running Fedora 36, I use both autofs and Systemd automount to mount NFS on demand. Gradually, I’m leaning toward just to use Systemd automount. Here is just a brain dump with an example of mounting an NFS share with Systemd autmount. Though, I had done this before, I found this blog post, available at [1], provides details on how to do this. Assumption The NFS server and share: banan.example.com:/srv/music The preferred local mount point: /srv/banan/music Create required Systemd unit files We will need 2 unit files: the mount unit and the automount unit. ...

I recently had a need to run Proxmox Virtual Environment (7.2-4) at home for a project. So far everything seemed to be straight forward, partially thanks to KVM technology used in Promox. However, I also learned a few things along the way too. The first thing that I had look up on the Internet to get it working is to activate (Promox) qemu-guest-agent. If you’re reading this, it’s likely you didn’t get it working on first trial either. ...

A quick note for me to remind myself how to stop/start network service on FreeBSD (13.0). To stop or start, run one of the following commands: # service netif stop # service netif start To restart, just replace stop or start with restart: # service netif restart I also just found out that the above commands will nto restarting the routing service, as they only stop/start/restart network. To restart the routing service on FreeBSD, run: ...