ComputerLocus's questions

您好，我在 Proxmox 中创建了一个 Ubuntu 20.04 和 18.04 容器，当我通过 Proxmox GUI 创建容器后尝试启动它们时，它们都返回相同的错误。

它们无法启动并返回以下错误消息：

Job for [email protected] failed because the control process exited with error code.
See "systemctl status [email protected]" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@100' failed: exit code 1

我发现另一个听起来相似的 serverfault 问题] 1，但是错误略有不同，我什至还没有到能够设置任何东西的步骤。这些是直接通过 Proxmox 的官方位置下载的干净的 Ubuntu 模板。此外，当我设置 Proxmox I 和容器时，我将所有内容都保留为默认值，包括所有存储内容。

我有点不清楚从这里去哪里或做什么。

我还按照错误消息指示的详细信息执行了journalctl -xe命令和systemctl status命令，结果如下：

# journalctl -xe
-- Support: https://www.debian.org/support
-- 
-- An ExecStart= process belonging to unit [email protected] has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Killing process 14587 (lxc-start) with signal SIGKILL.
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Killing process 14648 (apparmor_parser) with signal SIGKILL.
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit [email protected] has entered the 'failed' state with result 'exit-code'.
May 06 17:53:56 ns500282 systemd[1]: Failed to start PVE LXC Container: 100.
-- Subject: A start job for unit [email protected] has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit [email protected] has finished with a failure.
-- 
-- The job identifier is 173480 and the job result is failed.
May 06 17:54:00 ns500282 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: A start job for unit pvesr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit pvesr.service has begun execution.
-- 
-- The job identifier is 173490.
May 06 17:54:00 ns500282 systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit pvesr.service has successfully entered the 'dead' state.
May 06 17:54:00 ns500282 systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit pvesr.service has finished successfully.
-- 
-- The job identifier is 173490.

和

# systemctl status [email protected]
● [email protected] - PVE LXC Container: 100
   Loaded: loaded (/lib/systemd/system/[email protected]; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-05-06 17:53:56 EDT; 2min 19s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 14579 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)

May 06 17:53:54 ns500282 systemd[1]: Starting PVE LXC Container: 100...
May 06 17:53:56 ns500282 lxc-start[14579]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 874 Received container state "ABORTING" instead of "RUNNING"
May 06 17:53:56 ns500282 lxc-start[14579]: lxc-start: 100: tools/lxc_start.c: main: 329 The container failed to start
May 06 17:53:56 ns500282 lxc-start[14579]: lxc-start: 100: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
May 06 17:53:56 ns500282 lxc-start[14579]: lxc-start: 100: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority 
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Control process exited, code=exited, status=1/FAILURE
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Killing process 14587 (lxc-start) with signal SIGKILL.
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Killing process 14648 (apparmor_parser) with signal SIGKILL.
May 06 17:53:56 ns500282 systemd[1]: [email protected]: Failed with result 'exit-code'.
May 06 17:53:56 ns500282 systemd[1]: Failed to start PVE LXC Container: 100.

我有一个屏幕会话，我运行了几个窗口，这些窗口正在运行几个在终端窗口中运行控制台的应用程序（这就是为什么我在屏幕中运行它们的原因）。

我想杀死所有的窗口，然后添加两个新的窗口，基本上只是重新运行命令以再次启动程序。

由于这可能有点令人困惑，如果我只是尝试在命令行上手动执行此操作，我会这样做：

$ screen -x programs

$ (Hit Control-a + \ )

$ (Hit Control-a + c)

$ program1 args0 args1 #running first program again

$ (Hit Control-a + c)

$ program2 args0 args1 #running second program

从技术上讲，我什至不需要杀死现有的窗口，只需停止交互式窗口的运行。通常我在窗口中执行此操作时，我只需按 CTRL-D 并且程序停止运行。然后我再次运行程序。

我知道有命令可以按名称附加到现有的屏幕会话，我只是不知道如何使用它来发送相当于 CTRL+D 的命令，然后向它发送另一个命令。

我使用psql "service=subscription". 我如何使用该服务pg_dump？

我尝试执行以下操作： pg_dump -h "service=subscription" > /home/fogest/dump.out

然而这并没有奏效。

我应该怎么做？

编辑：当我执行以下操作时出现错误：

pg_dump -h "service=subscription" odyssey_prod > /u3/jhvisser/dump.out
pg_dump: [archiver (db)] connection to database "odyssey_prod" failed: could not translate host name "service=subscription" to address: Name or service not known

我正在尝试在刚获得的新 vps 上设置 postfix，这是第一次进行任何类型的电子邮件设置。尝试执行测试电子邮件时出现错误。我发布了我的配置和错误，我想知道我是否在某个地方犯了错误？我正在运行 Ubuntu 12.04 LTS VPS。

得到错误：

mail from:<jhvisser>
250 2.1.0 <jhvisser>... Sender ok
rcpt to:<jhvisser>
553 5.5.4 <jhvisser>... Domain name required for sender address jhvisser

使用配置：

# See /usr/share/postfix/main.cf.dist for a commented, more complete version
# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = yes

# Uncomment the next line to geneAug 23 10:15:36 jhvisser sm-mta[15093]: r7NEExQ1015093: from=<[email protected]>, size=5, class=0, nrcpts=1, proto=SMTP, daemon=MTA-v4, relay=localhost.localdomain [127.0.0.1]

8 月 23 日 10:15:36 jhvisser sm-mta[15093]: r7NEExQ1015093: from=, size=5, class=0, nrcpts=1, proto=SMTP, daemon=MTA-v4, relay=localhost.localdomain [127.0. 0.1] 率“延迟邮件”警告 #delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file = /etc/ssl/certs/smtpd.crt
smtpd_tls_key_file = /etc/ssl/private/smtpd.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

myhostname = jhvisser.com
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = jhvisser.com
mydestination = jhvisser.com, localhost.com, , localhost
relayhost = 
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_command = 
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all
home_mailbox = Maildir/
smtpd_sasl_local_domain = 
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtp_tls_security_level = may
smtpd_tls_security_level = may
smtpd_tls_auth_only = no
smtp_tls_note_starttls_offer = yes
smtpd_tls_CAfile = /etc/ssl/certs/cacert.pem
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom

新错误：

helo localhost
250 jhvisser.com Hello localhost.localdomain [127.0.0.1], pleased to meet you
mail from:<[email protected]>
250 2.1.0 <[email protected]>... Sender ok
rcpt to:<[email protected]>
250 2.1.5 <[email protected]>... Recipient ok
data
354 Enter mail, end with "." on a line by itself
test
.
421 4.3.0 collect: Cannot write ./dfr7NDpBPF014521 (bfcommit, uid=0, gid=112): No such file or directory
Connection closed by foreign host.

日志：

Aug 23 10:15:36 jhvisser sm-mta[15093]: r7NEExQ1015093: from=<[email protected]>, size=5, class=0, nrcpts=1, proto=SMTP, daemon=MTA-v4, relay=localhost.localdomain [127.0.0.1]