High resource usage normal?

[justpowershell]

My zilean container sits at 100% of two cores @ 3.6Ghz and 1.9G of RAM. The two commands are /app/scraper dmm-sync. Logs show it is churning through titles and Riven seems to be getting new content, so I am curious if the high resource utilization is expected?

[that-9uy]

Your Zilean may be compromised, if you notice very high CPU usage on Zilean Postgres container. Someone has managed to access this container and use it to start an xmr miner using your cpu.

Please save the following script as zileanfix.py and do python3 zileanfix.py {newusername} {newpassword}

This will change the default username and password to the one you set in the command above.
This script will edit your Zilean docker compose with the new values you set in the command, bring down Zilean and compose it up with the fresh values as well as removing the ports section.

import sys
import yaml
import subprocess

# Check arguments
if len(sys.argv) != 3:
    print("Usage: python update_postgres_credentials.py <new_username> <new_password>")
    sys.exit(1)

new_username = sys.argv[1]
new_password = sys.argv[2]

compose_path = '/opt/zilean/docker-compose.yml'
db_name = 'zilean'  # Default postgres database (change if your app uses a different DB)

# Load existing compose.yaml
with open(compose_path, 'r') as f:
    compose = yaml.safe_load(f)

# Update postgres service env vars
postgres_env = compose['services']['zilean-postgres']['environment']
postgres_env['POSTGRES_USER'] = new_username
postgres_env['POSTGRES_PASSWORD'] = new_password

# Update zilean connection string
zilean_env = compose['services']['zilean']['environment']
conn_string = zilean_env['Zilean__Database__ConnectionString']

parts = conn_string.split(";")
new_parts = []
for part in parts:
    if part.startswith("Username="):
        new_parts.append(f"Username={new_username}")
    elif part.startswith("Password="):
        new_parts.append(f"Password={new_password}")
    else:
        new_parts.append(part)
new_conn_string = ";".join(new_parts)
zilean_env['Zilean__Database__ConnectionString'] = new_conn_string

# Save updated compose.yaml
with open(compose_path, 'w') as f:
    yaml.dump(compose, f, default_flow_style=False)

print(f"✅ Updated compose.yaml with username: {new_username} and password: {new_password}")

# Restart docker-compose services
try:
    subprocess.run(["docker", "compose", "-f", compose_path, "down"], check=True)
    subprocess.run(["docker", "compose", "-f", compose_path, "up", "-d"], check=True)
    print("✅ Docker Compose services restarted successfully.")
except subprocess.CalledProcessError:
    print("❌ Error restarting Docker Compose services.")
    sys.exit(1)

# Drop and recreate database owned by new user
try:
    # Drop database - connecting to default 'postgres' DB as superuser 'postgres'
    subprocess.run([
        "docker", "exec", "zilean-postgres",
        "psql", "-U", "postgres", "-d", "postgres",
        "-c", f"DROP DATABASE IF EXISTS {db_name};"
    ], check=True)

    # Create database owned by new user
    subprocess.run([
        "docker", "exec", "zilean-postgres",
        "psql", "-U", "postgres", "-d", "postgres",
        "-c", f"CREATE DATABASE {db_name} OWNER {new_username};"
    ], check=True)

    print(f"✅ Dropped and recreated database '{db_name}' owned by {new_username}")

except subprocess.CalledProcessError:
    print("❌ Failed to drop/recreate database inside container.")
    sys.exit(1)

[samandjtnc]

For me it is scraper that is gobbling up resources:

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND

  24414 root      20   0  260.5g 842708 143048 S 191.4   5.2   3:10.04 scraper

(I did take the steps above but this is still my result)

[smoofus]

Same here. Set up a new instance yesterday and scraper dmm-sync has been chugging through releases/imdb matching for a little over 24 hours now. Maybe it just takes some time for the initial sync to complete before it calms down?