Kobros Tech — Real-World Odoo & Linux Solutions

How to Run Odoo as a Systemd Service (Production Setup Guide) When deploying Odoo on a Linux server, running it manually using odoo-bin works for development, but it is not suitable for production environments. To ensure reliability, auto-restart, and proper process management, Odoo should be run as a systemd service. This topic is frequently discussed in community threads such as: Run Odoo as a Service (Stack Overflow) . ⚠️ Why Not Run Odoo Manually? Starting Odoo manually using ./odoo-bin has several limitations: No automatic restart on crash No boot-time startup No centralized logging management Manual process management required For production environments, this approach is not reliable. 🚀 Recommended Approach: Systemd Service Modern Linux distributions (Ubuntu 16.04+, Debian 9+, etc.) use systemd for service management. Odoo should be configured as a systemd service unit. ⚙️ Example Odoo Systemd Service File [Unit] Description=Odoo E...

How to Manage Odoo Backups Properly: Built-in Backup vs OCA Storage Backend Odoo provides a built-in database backup feature accessible from the interface. While this works for small environments or development setups, it is not sufficient for production systems where reliability, automation, and external storage are required. This topic is commonly discussed in the context of Odoo database backups, including questions such as: How to backup Odoo database from within Odoo . ⚠️ Limitations of Odoo Built-in Backup Odoo’s default backup system generates a ZIP file containing the database dump and filestore. While useful, it has several limitations in real-world production environments: No automatic scheduling or rotation Backups must be triggered manually or via custom scripts Backups are stored locally on the server by default No native integration with cloud storage providers No centralized backup strategy across multiple instances As a result, relying ...

How to Use Odoo Scaffolding to Quickly Generate a Custom Module When starting Odoo development, one of the first repetitive tasks is creating the basic structure of a custom module. Odoo provides a built-in command called scaffolding that generates this structure automatically. This feature is commonly referenced in discussions such as the Stack Overflow question on Odoo scaffolding: Odoo Scaffolding Discussion . 🚀 What is Odoo Scaffolding? Odoo scaffolding is a command-line utility that generates a ready-to-use module template. Instead of manually creating folders, files, and boilerplate code, the scaffold command builds the standard structure for you. This helps developers start faster and ensures consistency across modules. ⚙️ Basic Scaffolding Command In modern Odoo versions (v10 and above), scaffolding is done using odoo-bin : ./odoo-bin scaffold module_name /path/to/custom_addons Where: module_name → Name of your new module /path/to/custom_a...

Fixing GCC Exit Status 1 During Python Package Installation on Linux When installing Python packages on Linux systems, especially those with native extensions, you may encounter the following build failure: error: Setup script exited with error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 This error appears during the compilation phase of a Python package and indicates that the C extension build process has failed. It is not a GCC malfunction itself, but rather a symptom of missing system-level dependencies required to compile the package. Root Cause In most cases, the build process fails because the compiler cannot locate required header files or development libraries. These dependencies vary depending on the Python package being installed. Typical missing components include: Python development headers ( Python.h ) System build tools ( gcc , make ) OpenSSL or cryptography dependencies Database client libraries (PostgreSQL, MySQL, et...

How to Close a Service Running on a Specific Port in Linux If you have a service running on a specific port (like 8080 ) and need to stop it, you can identify the process and terminate it safely. Step 1: Find the Process Using the Port Use the following command to find the process ID (PID): lsof -i :8080 Example output: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME node 1234 user 21u IPv4 12345 0t0 TCP *:8080 (LISTEN) Step 2: Kill the Process Once you have the PID, terminate the process: kill -9 1234 Replace 1234 with your actual PID. Alternative: One-liner Command You can combine the steps into a single command: kill -9 $(lsof -t -i:8080) Step 3: Verify the Port is Closed Check again to confirm the port is no longer in use: ss -tuln | grep 8080 If no output is returned, the port is successfully closed. Important Notes Avoid using -9 unless necessary; try kill PID first for a graceful shutdown. Make sure the process...

How to Check if Port 8080 is Open in Linux When working with servers or local development environments, you may need to verify whether a specific port (like 8080 ) is open and listening. This is especially common when running web applications, APIs, or services. Method 1: Using netstat The netstat command is a common way to check open ports. netstat -tuln | grep 8080 If port 8080 is open, you will see output similar to: tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN Method 2: Using ss (Recommended) The ss command is faster and more modern than netstat: ss -tuln | grep 8080 Method 3: Using lsof You can also check which process is using the port: lsof -i :8080 This will show the process name and PID (Process ID). Method 4: Using nc (Netcat) To test if the port is open externally: nc -zv localhost 8080 Conclusion Checking if a port is open is essential for debugging network services. The ss and lsof commands are usually the most helpful for ...