# FAQ

> Frequently asked questions about Pigsty NODE module

---

LLMS index: [llms.txt](/llms.txt)

---

----------------

## How to configure NTP service?

> NTP is critical for various production services. If NTP is not configured, you can use public NTP services or the Chronyd on the admin node as the time standard.

If your nodes already have NTP configured, you can preserve the existing configuration without making any changes by setting `node_ntp_enabled` to `false`.

Otherwise, if you have Internet access, you can use public NTP services such as `pool.ntp.org`.

If you don't have Internet access, you can use the following approach to ensure all nodes in the environment are synchronized with the admin node, or use another internal NTP time service.

```bash
node_ntp_servers:                 # NTP servers in /etc/chrony.conf
  - pool cn.pool.ntp.org iburst
  - pool ${admin_ip} iburst       # assume non-admin nodes do not have internet access, at least sync with admin node
```

----------------

## How to force sync time on nodes?

Use `chronyc` to sync time. You must configure the NTP service first.

```bash
ansible all -b -a 'chronyc -a makestep'     # sync time
```

You can replace `all` with any group or host IP address to limit the execution scope.



----------------

## Remote nodes are not accessible via SSH?

If the target machine is hidden behind an SSH jump host, or some customizations prevent direct access using `ssh ip`, you can use [Ansible connection parameters](https://docs.ansible.com/ansible/latest/inventory_guide/connection_details.html) to specify various SSH connection options, such as:

```bash
pg-test:
  vars: { pg_cluster: pg-test }
  hosts:
    10.10.10.11: {pg_seq: 1, pg_role: primary, ansible_host: node-1 }
    10.10.10.12: {pg_seq: 2, pg_role: replica, ansible_port: 22223, ansible_user: admin }
    10.10.10.13: {pg_seq: 3, pg_role: offline, ansible_port: 22224 }
```



----------------

## Password required for remote node SSH and SUDO?

**When performing deployments and changes**, the admin user used **must** have `ssh` and `sudo` privileges for all nodes. Passwordless login is not required.

You can pass ssh and sudo passwords via the `-k|-K` parameters when executing playbooks, or even use another user to run playbooks via `-e`[`ansible_host`](/docs/node/param#connect)`=<another_user>`.

However, Pigsty strongly recommends configuring SSH **passwordless login** with passwordless `sudo` for the admin user.



----------------

## How to create a dedicated admin user with an existing admin user?

Use the following command to create a new standard admin user defined by [`node_admin_username`](/docs/node/param#node_admin_username) using an existing admin user on that node.

```bash
./node.yml -k -K -e ansible_user=<another_admin> -t node_admin
```

----------------

## How to expose services using HAProxy on nodes?

You can use [`haproxy_services`](/docs/node/param#haproxy_services) in the configuration to expose services, and use `node.yml -t haproxy_config,haproxy_reload` to update the configuration.

Here's an example of exposing Silo: [Silo Service Access](/docs/minio/config#expose-service)



----------------

## Why are all my /etc/yum.repos.d/* files gone?

Pigsty builds a local software repository on infra nodes that includes all dependencies. All regular nodes will reference and use the local software repository on Infra nodes according to the default configuration of [`node_repo_modules`](/docs/node/param#node_repo_modules) as `local`.

This design avoids Internet access and enhances installation stability and reliability. All original repo definition files are moved to the `/etc/yum.repos.d/backup` directory; you can copy them back as needed.

If you want to preserve the original repo definition files during regular node installation, set [`node_repo_remove`](/docs/node/param#node_repo_remove) to `false`.

If you want to preserve the original repo definition files during Infra node local repo construction, set [`repo_remove`](/docs/infra/param#repo_remove) to `false`.



----------------

## Why did my command line prompt change? How to restore it?

The shell command line prompt used by Pigsty is specified by the environment variable `PS1`, defined in the `/etc/profile.d/node.sh` file.

If you don't like it and want to modify or restore it, you can remove this file and log in again.




----------------

## Why did my hostname change?

Pigsty will modify your node hostname in two situations:

* [`nodename`](/docs/node/param#nodename_overwrite) value is explicitly defined (default is empty)
* The [**`PGSQL`**](/docs/pgsql) module is declared on the node and the [**`node_id_from_pg`**](/docs/node/param#node_id_from_pg) parameter is enabled (default is `true`)

If you don't want the hostname to be modified, you can set [**`nodename_overwrite`**](/docs/node/param#nodename_overwrite) to `false` at the global/cluster/instance level (default is `true`).

For details, see the [**`NODE_ID`**](/docs/node/param#node_id) section.




----------------

## What compatibility issues exist with Tencent OpenCloudOS?

The `softdog` kernel module is not available on OpenCloudOS and needs to be removed from `node_kernel_modules`. Add the following configuration item to the global variables in the config file to override:

```yaml
node_kernel_modules: [ ip_vs, ip_vs_rr, ip_vs_wrr, ip_vs_sh ]
```


----------------

## What common issues exist on Debian systems?

When using Pigsty on Debian/Ubuntu systems, you may encounter the following issues:

**Missing locale**

If the system reports locale-related errors, you can fix them with the following command:

```bash
localedef -i en_US -f UTF-8 en_US.UTF-8
```

**Missing rsync tool**

Pigsty relies on rsync for file synchronization. If the system doesn't have it installed, you can install it with:

```bash
apt-get install rsync
```