Zammad: 由于PGConsumeInput（）中的文件描述符错误，调度程序未运行

创建于 2017-09-11  ·  23评论  ·  资料来源: zammad/zammad

从1.6.x升级到2.1.x之后，我们注意到邮件不再被提取。 这是当我们注意到调度程序的PostgreSQL连接遇到错误时。

资讯：

  • 使用的Zammad版本：2.1.1-1505128598.ef38800b.jessie
  • 二手Zammad安装源：软件包
  • 操作系统：Debian 8
  • PostgreSQL版本：9.4.13-0 + deb8u1

健康

channel is active but not fetched for 1 hour
channel is active but not fetched for 1 hour
channel is active but not fetched for 1 hour
channel is active but not fetched for 1 hour
scheduler not running

日志

==> /var/log/zammad/scheduler_err.log <==
ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() could not receive data from server: Bad file descriptor
: SELECT "delayed_jobs".* FROM "delayed_jobs"
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:598:in `async_exec'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:598:in `block in exec_no_cache'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract_adapter.rb:590:in `block in log'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activesupport-5.0.5/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract_adapter.rb:583:in `log'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:598:in `exec_no_cache'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:585:in `execute_and_clear'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql/database_statements.rb:103:in `exec_query'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:377:in `select_prepared'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:39:in `select_all'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract/query_cache.rb:95:in `select_all'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/querying.rb:39:in `find_by_sql'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation.rb:702:in `exec_queries'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation.rb:583:in `load'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation.rb:260:in `records'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation/delegation.rb:38:in `each'
  /opt/zammad/app/models/scheduler.rb:78:in `cleanup'
  /opt/zammad/app/models/scheduler.rb:24:in `threads'
  script/scheduler.rb:66:in `block in <top (required)>'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons/application.rb:266:in `block in start_proc'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons/application.rb:275:in `start_proc'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons/application.rb:296:in `start'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons/controller.rb:56:in `run'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons.rb:197:in `block in run_proc'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons/cmdline.rb:92:in `catch_exceptions'
  /opt/zammad/vendor/bundle/ruby/2.4.0/gems/daemons-1.2.4/lib/daemons.rb:196:in `run_proc'
  script/scheduler.rb:49:in `<top (required)>'
==> /var/log/zammad/scheduler_out.log <==
bundler: failed to load command: script/scheduler.rb (script/scheduler.rb)

PostgreSQL是可连接的，并且工作正常。

picture mweinelt

最有用的评论

@martini我可以确认更新是否成功。 非常感谢你！

稍后将尝试降级到2.0。

picture mweinelt 于 2017-09-26
❤2 👍2

所有23条评论

当temp或数据存储上没有剩余空间时，通常会发生这种情况。 我不认为这与Zammad有关。 追溯直接来自
活动记录

我建议检查文件系统（空间和索引节点）并在PG数据库上执行检查。

编辑：
当您重新启动Scheduler和Postgresql时会发生什么？

笔记：
请不要在生产中使用开发分支！ 2.0稳定

hanneshal picture hanneshal 于 2017-09-12

文件系统看起来几乎不满。

hexa<strong i="6">@tickets</strong>:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1       20G  6.2G   13G  34% /
udev             10M     0   10M   0% /dev
tmpfs           502M   45M  457M   9% /run
tmpfs           1.3G   16K  1.3G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           1.3G     0  1.3G   0% /sys/fs/cgroup
tmpfs           251M     0  251M   0% /run/user/2000
hexa<strong i="7">@tickets</strong>:~$ df -i
Filesystem      Inodes IUsed   IFree IUse% Mounted on
/dev/xvda1     1310720 97329 1213391    8% /
udev            314738   268  314470    1% /dev
tmpfs           320664   313  320351    1% /run
tmpfs           320664     5  320659    1% /dev/shm
tmpfs           320664     3  320661    1% /run/lock
tmpfs           320664    13  320651    1% /sys/fs/cgroup
tmpfs           320664     4  320660    1% /run/user/2000

PostgreSQL似乎没有任何内部检查机制。 重启两个都不会改变这种情况。

我知道不要使用development分支，但是我们需要从1.6开始，因为我们需要LDAP，然后忘记固定版本。

mweinelt picture mweinelt 于 2017-09-12

PostgreSQL显然也已启动并可以访问。 这也适用于/opt/zammad/config/database.yml设置的凭据。

root<strong i="7">@tickets</strong>:/home/hexa# sudo -u postgres psql
psql (9.4.13)
Type "help" for help.

postgres=# \connect zammad
You are now connected to database "zammad" as user "postgres".

zammad=# \dt
                      List of relations
 Schema |                Name                | Type  | Owner  
--------+------------------------------------+-------+--------
 public | activity_streams                   | table | zammad
 public | ar_internal_metadata               | table | zammad
 public | authorizations                     | table | zammad
 public | avatars                            | table | zammad
 public | calendars                          | table | zammad
 public | channels                           | table | zammad
 public | chat_agents                        | table | zammad
 public | chat_messages                      | table | zammad
 public | chat_sessions                      | table | zammad
 public | chat_topics                        | table | zammad
 public | chats                              | table | zammad
 public | cti_caller_ids                     | table | zammad
 public | cti_logs                           | table | zammad
 public | delayed_jobs                       | table | zammad
 public | email_addresses                    | table | zammad
 public | external_credentials               | table | zammad
 public | external_syncs                     | table | zammad
 public | groups                             | table | zammad
 public | groups_users                       | table | zammad
 public | histories                          | table | zammad
 public | history_attributes                 | table | zammad
 public | history_objects                    | table | zammad
 public | history_types                      | table | zammad
 public | http_logs                          | table | zammad
 public | import_jobs                        | table | zammad
 public | jobs                               | table | zammad
 public | karma_activities                   | table | zammad
 public | karma_activity_logs                | table | zammad
 public | karma_users                        | table | zammad
 public | link_objects                       | table | zammad
 public | link_types                         | table | zammad
 public | links                              | table | zammad
 public | locales                            | table | zammad
 public | macros                             | table | zammad
 public | network_categories                 | table | zammad
 public | network_categories_moderator_users | table | zammad
 public | network_category_subscriptions     | table | zammad
 public | network_category_types             | table | zammad
 public | network_item_comments              | table | zammad
 public | network_item_plus                  | table | zammad
 public | network_item_subscriptions         | table | zammad
 public | network_items                      | table | zammad
 public | network_privacies                  | table | zammad
 public | networks                           | table | zammad
 public | notifications                      | table | zammad
 public | oauth_access_grants                | table | zammad
 public | oauth_access_tokens                | table | zammad
 public | oauth_applications                 | table | zammad
 public | object_lookups                     | table | zammad
 public | object_manager_attributes          | table | zammad
 public | online_notifications               | table | zammad
 public | organizations                      | table | zammad
 public | organizations_users                | table | zammad
 public | overviews                          | table | zammad
 public | overviews_groups                   | table | zammad
 public | overviews_roles                    | table | zammad
 public | overviews_users                    | table | zammad
 public | package_migrations                 | table | zammad
 public | packages                           | table | zammad
 public | permissions                        | table | zammad
 public | permissions_roles                  | table | zammad
 public | postmaster_filters                 | table | zammad
 public | recent_views                       | table | zammad
 public | report_profiles                    | table | zammad
 public | roles                              | table | zammad
 public | roles_groups                       | table | zammad
 public | roles_users                        | table | zammad
 public | schedulers                         | table | zammad
 public | schema_migrations                  | table | zammad
 public | sessions                           | table | zammad
 public | settings                           | table | zammad
 public | signatures                         | table | zammad
 public | slas                               | table | zammad
 public | stats_stores                       | table | zammad
 public | store_files                        | table | zammad
 public | store_objects                      | table | zammad
 public | store_provider_dbs                 | table | zammad
 public | stores                             | table | zammad
 public | tag_items                          | table | zammad
 public | tag_objects                        | table | zammad
 public | tags                               | table | zammad
 public | taskbars                           | table | zammad
 public | templates                          | table | zammad
 public | templates_groups                   | table | zammad
 public | text_modules                       | table | zammad
 public | text_modules_groups                | table | zammad
 public | ticket_article_flags               | table | zammad
 public | ticket_article_senders             | table | zammad
 public | ticket_article_types               | table | zammad
 public | ticket_articles                    | table | zammad
 public | ticket_counters                    | table | zammad
 public | ticket_flags                       | table | zammad
 public | ticket_priorities                  | table | zammad
 public | ticket_state_types                 | table | zammad
 public | ticket_states                      | table | zammad
 public | ticket_time_accountings            | table | zammad
 public | tickets                            | table | zammad
 public | tokens                             | table | zammad
 public | translations                       | table | zammad
 public | triggers                           | table | zammad
 public | type_lookups                       | table | zammad
 public | user_devices                       | table | zammad
 public | users                              | table | zammad
(103 rows)
mweinelt picture mweinelt 于 2017-09-12

今天，我在Mac OS 10.12.6和Develop（Zammad 2.1）上都具有相同的功能（但它在before之前的几天就可以使用）。 所有人都在期待调度程序的正常运行（导轨c，导轨s等）。

martini picture martini 于 2017-09-15

我具有从1.5到2.0的相同升级100％CPU使用率，并且此错误

尾部：scheduler_err.log：Datei abgeschnitten
ActiveRecord :: StatementInvalid：PG :: ConnectionBad：PQconsumeInput（）无法从服务器接收数据：错误的文件描述符
：选择“ delayed_jobs”。*从“ delayed_jobs”
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:598：在exec_no_cache的async_exec' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:598:in块中
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract_adapter.rb:590：在block in log' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activesupport-5.0.5/lib/active_support/notifications/instrumenter.rb:21:in工具中
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract_adapter.rb:583:in log' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:598:in exec_no_cache'
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql_adapter.rb:585:in execute_and_clear' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/postgresql/database_statements.rb:103:in exec_query'
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:377:in select_prepared' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract/database_statements.rb:39:in select_all'
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/connection_adapters/abstract/query_cache.rb:95:in select_all' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/querying.rb:39:in find_by_sql'
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation.rb:702:in exec_queries' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation.rb:583:in load'
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation.rb:260:in records' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/activerecord-5.0.5/lib/active_record/relation/delegation.rb:38:in '
/opt/zammad/app/models/scheduler.rb:78:in cleanup' /opt/zammad/app/models/scheduler.rb:24:in线程'
script / scheduler.rb：66：in在块中

Hagelsturm picture Hagelsturm 于 2017-09-21

@Hagelsturm哪个操作系统？ 哪个过程需要100％？

martini picture martini 于 2017-09-21

在我们的例子中是script/scheduler.rb start -t 。

mweinelt picture mweinelt 于 2017-09-21

在我们的例子中是script/scheduler.rb start -t

那也是我的立场。 通常，调度程序在守护程序模式下运行（ script/scheduler.rb start或script/scheduler.rb stop ）。

script/scheduler.rb start -t通常仅用于开发人员，因为调度程序未在后台运行（作为守护程序）。

@mweinelt对我来说，一个问题是，为什么要使用-t ？

JFI：调度程序在后台（作为守护程序）对我来说工作正常。

martini picture martini 于 2017-09-21

我正在运行2.1.1-1505985142.807a1d88.jessie因为我忘了固定到一个稳定的版本。 -t选项必须来自服务文件，在这方面我没有做任何更改。

root<strong i="8">@tickets</strong>:/opt/zammad# grep -ri "scheduler.rb start" *
contrib/systemd/zammad-scheduler.service:ExecStart=/bin/bash -l -c "${BUNDLE_BINARY} exec script/scheduler.rb start -t"
Procfile:worker: bundle exec script/scheduler.rb start -t
Procfile.frontend:worker: bundle exec ruby script/scheduler.rb start -t
script/init-script-normal-user-rvm-fedora:    script/scheduler.rb start &> /dev/null && echo_success || echo_failure
script/init.d/zammad:  execute "RAILS_ENV=production script/scheduler.rb start $SCHEDULER_OPTS"
script/build/test_startup.sh:bundle exec script/scheduler.rb start
script/local_browser_tests.sh:script/scheduler.rb start
vendor/pkgr/processes/worker:exec bundle exec script/scheduler.rb start -t $@
mweinelt picture mweinelt 于 2017-09-21

我昨天也使用Debian 8，我也尝试了版本9
但是错误是一样的
我什么都没修改-t来自软件包而不是我

Hagelsturm picture Hagelsturm 于 2017-09-21

100％的过程是Ruby
脚本/scheduler.rb开始-t
每次都开始崩溃

Hagelsturm picture Hagelsturm 于 2017-09-21

来自scheduler.rb-帮助：

  • “ -t，--ontop保持在最前面（不守护）”
monotek picture monotek 于 2017-09-21

也许但调度程序始终崩溃
死了，您认为原因是ontop参数吗？

Hagelsturm picture Hagelsturm 于 2017-09-21

@哈格尔斯图姆
不，只是想弄清楚它的作用。 没有看到马提尼酒的答案。
守护进程是由systemd完成的，因此通常没有问题。

@马蒂尼
如果我没记错的话，使用“ -t”是因为systemd认为调度程序从单元文件进入背景时会失败并停止。

@mweinelt
如果您使用的是2.1.1，则位于开发库中。
无法在其中固定稳定的包装。
使用稳定的仓库来获得稳定的软件包： https :

monotek picture monotek 于 2017-09-21

@monotek
如果我没有记错的话，设置Type=forking应该允许不使用-t 。

关于降级到稳定版本（2.0.x）：
如果没有最近的备份，我将不得不还原一些迁移，对吗？

mweinelt picture mweinelt 于 2017-09-21

感谢您的提示。 稍后将尝试更改它。 不确定是否可以在packager.io中使用。

monotek picture monotek 于 2017-09-22

好吧，我现在使用2.0版
但是现在我的电子邮件频道有问题

电子邮件::通知输出无法使用频道::驱动程序:: Smtp：＃<：econnrefused：i =“ 6”>

我无法检查设置，因为该帐户为空:-(

Hagelsturm picture Hagelsturm 于 2017-09-22

ticket
频道处于活动状态，但未获取1小时
频道：Email :: Notification out无法使用Channel :: Driver :: Smtp：＃<：econnrefused：i =“ 7”>

如何设置新的CLI？

Hagelsturm picture Hagelsturm 于 2017-09-22

@Hagelsturm尝试检查您的smtp设置，可能您的电子邮件通道设置中的SMTP主机参数不存在。 另外，由于您的问题是一个新问题，您应该创建一个新问题吗？

muhammadn picture muhammadn 于 2017-09-25

你好呀！ 这里有同样的问题。 我从＃1473到达这里。 我安装了2.0版，但无法在电子邮件频道配置上添加新的电子邮件帐户，这可能与@Hagelsturm的最新评论有关。

edneymatias picture edneymatias 于 2017-09-25

如果没有最近的备份，我将不得不还原一些迁移，对吗？

@mweinelt对不起，我没有看到此反馈。 目前，稳定和开发之间没有数据库迁移。 因此，现在您可以在稳定/主控之间进行切换，而不会出现任何问题。

无论如何，似乎我已经解决了“ PGConsumeInput中的错误文件描述符”问题。 因此，如果您先更新开发（在切换回稳定之前）就可以了！

感谢您的反馈！

-马丁

martini picture martini 于 2017-09-26
❤1

@Hagelsturm JFI您的电子邮件问题与此调度程序问题

martini picture martini 于 2017-09-26

@martini我可以确认更新是否成功。 非常感谢你！

稍后将尝试降级到2.0。

mweinelt picture mweinelt 于 2017-09-26
❤2 👍2
此页面是否有帮助？
0 / 5 - 0 等级

相关问题

alveolus picture alveolus  ·  3评论
strey picture strey  ·  3评论
minions1291 picture minions1291  ·  3评论
fthommen picture fthommen  ·  3评论
robwilc picture robwilc  ·  3评论