Spinnaker_deployment_error

2021年7月1日

| Kubernetes CI/CD Error

腾讯云coding平台部署错误

Check that the Docker image name above matches the name used in the image field of your manifest.Failing the stage as this is likely a configuration error.

是因为【启动所需制品】下【仓库】的镜像配置和自定义变量【dockerImage】的镜像名不一致。

……

阅读全文

github push error

2021年2月25日

| Error

git push origin master后出错
error: src refspec master does not match any
error: failed to push some refs to 'https://github.com/test.test.git'

原来github的master已经改成main了。。。

……

阅读全文

gitlab send mail err

2021年2月25日

| Error

SendAsDenied; gitlib@example.com not allowed to send as gitlab@git.example.com; STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message

遇到一个gitlab发送邮件的错误，原因是因为gitlab_rails['gitlab_email_from'] = 'gitlab@example.com'该参数没有设置。

……

阅读全文

缺少LIBNCURSES.SO.5文件一例

2021年2月16日

| Error

系统信息如下：

Linux 4.14.104-95.84.amzn2.x86_64 #1 SMP x86_64 GNU/Linux

执行 sudo /usr/local/mysql/bin/mysql -uroot -p 报出如下错误：

……

阅读全文

Rabbitmq_权限问题

2020年7月23日

| Error RabbitMQ

发布消息时报如下错误：

pika.exceptions.ChannelClosedByBroker: (403, “ACCESS_REFUSED - access to queue ‘hello’ in vhost ‘/’ refused for user ‘admin’

……

阅读全文

zabbix监控ipmi的一个报错

2019年10月16日

| Zabbix Error

zabbix端item某项出现Value should be a JSON object错误。

……

阅读全文

Rpm_install_err

2019年6月29日

| Linux Error

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61


yum instal gcc

Protected multilib versions: libgomp-4.8.5-28.el7.i686 != libgomp-4.8.5-28.el7_5.1.x86_64

[root@v-ct-dsjpaas-app-02 memcached-1.5.12]# rpm --erase --nodeps libgomp
[root@v-ct-dsjpaas-app-02 memcached-1.5.12]# yum install libgomp
[root@v-ct-dsjpaas-app-02 memcached-1.5.12]# yum install gcc

Error: Package: libstdc++-devel-4.8.5-28.el7.x86_64 (c7-media)
           Requires: libstdc++(x86-64) = 4.8.5-28.el7
           Installed: libstdc++-4.8.5-28.el7_5.1.x86_64 (@updates)
               libstdc++(x86-64) = 4.8.5-28.el7_5.1
           Available: libstdc++-4.8.5-28.el7.x86_64 (c7-media)
               libstdc++(x86-64) = 4.8.5-28.el7
Error: Package: gcc-c++-4.8.5-28.el7.x86_64 (c7-media)
           Requires: libstdc++ = 4.8.5-28.el7
           Installed: libstdc++-4.8.5-28.el7_5.1.i686 (@updates)
               libstdc++ = 4.8.2-16.el7_5
               libstdc++ = 4.8.5-28.el7_5.1
           Available: libstdc++-4.8.5-28.el7.i686 (c7-media)
               libstdc++ = 4.8.5-28.el7
               libstdc++ = 4.8.2-16.el7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

 [root@v-ct-dsjpaas-app-03 nginx-1.10.3]# rpm -e --nodeps libstdc++-4.8.5-28.el7_5.1.x86_64
[root@v-ct-dsjpaas-app-03 nginx-1.10.3]# yum install gcc-c++

Error:  Multilib version problems found. This often means that the root
       cause is something else and multilib version checking is just
       pointing out that there is a problem. Eg.:
       
         1. You have an upgrade for libstdc++ which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of libstdc++ of the
            different architecture. If you exclude the bad architecture
            yum will tell you what the root cause is (which package
            requires what). You can try redoing the upgrade with
            --exclude libstdc++.otherarch ... this should give you an error
            message showing the root cause of the problem.
       
         2. You have multiple architectures of libstdc++ installed, but
            yum can only see an upgrade for one of those architectures.
            If you don't want/need both architectures anymore then you
            can remove the one with the missing update and everything
            will work.
       
         3. You have duplicate versions of libstdc++ installed already.
            You can use "yum check" to get yum show these errors.
       
       ...you can also use --setopt=protected_multilib=false to remove
       this checking, however this is almost never the correct thing to
       do as something else is very likely to go wrong (often causing
       much more problems).
       
       Protected multilib versions: libstdc++-4.8.5-28.el7.x86_64 != libstdc++-4.8.5-28.el7_5.1.i686
[root@v-ct-dsjpaas-app-03 nginx-1.10.3]# rpm -e --nodeps libstdc++
                                         yum install libstdc++.so.6
[root@v-ct-dsjpaas-app-03 nginx-1.10.3]# yum install gcc-c++

rpm -e --nodeps libcom_err

……

阅读全文

显卡故障日志分析

2018年6月23日

| Linux Error

物理机宕机，查看有如下日志：

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14


Jul 23 18:04:14 10.16.73.45 [19259390.583100] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 3
Jul 23 18:04:14 10.16.73.45 [19259390.587458] {1}[Hardware Error]: event severity: fatal
Jul 23 18:04:14 10.16.73.45 [19259390.589789] {1}[Hardware Error]: Error 0, type: fatal
Jul 23 18:04:14 10.16.73.45 [19259390.592093] {1}[Hardware Error]: section_type: PCIe error
Jul 23 18:04:14 10.16.73.45 [19259390.594490] {1}[Hardware Error]: port_type: 4, root port
Jul 23 18:04:14 10.16.73.45 [19259390.596754] {1}[Hardware Error]: version: 1.16
Jul 23 18:04:14 10.16.73.45 [19259390.599014] {1}[Hardware Error]: command: 0x0547, status: 0x4010
Jul 23 18:04:14 10.16.73.45 [19259390.601243] {1}[Hardware Error]: device_id: 0000:00:02.0
Jul 23 18:04:14 10.16.73.45 [19259390.603379] {1}[Hardware Error]: slot: 6
Jul 23 18:04:14 10.16.73.45 [19259390.605558] {1}[Hardware Error]: secondary_bus: 0x03
Jul 23 18:04:14 10.16.73.45 [19259390.607726] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f04
Jul 23 18:04:14 10.16.73.45 [19259390.610003] {1}[Hardware Error]: class_code: 000406
Jul 23 18:04:14 10.16.73.45 [19259390.612194] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x0003
Jul 23 18:04:14 10.16.73.45 [19259390.616976] Kernel panic – not syncing: Fatal hardware error!

知识点：

……

阅读全文

MYSQL ERRS

2017年2月16日

| Error MySQL

001

cripts/mysql_install_db –no-defaults –datadir=/mysql/my_cluster/mysqld_data/
FATAL ERROR: please install the following Perl modules before executing scripts/mysql_install_db:
Data::Dumper

yum install perl-Data-Dumper.x86_64

002

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect…

set global max_allowed_packet=100M
将此值设置大些

003

[root@localhost ~]# rpm -ivh mysql-community-server-5.7.21-1.el6.x86_64.rpm
warning: mysql-community-server-5.7.21-1.el6.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 5072e1f5: NOKEY
error: Failed dependencies:
libsasl2.so.2()(64bit) is needed by mysql-community-server-5.7.21-1.el6.x86_64

rpm -ivh https://rpmfind.net/linux/Mandriva/devel/cooker/x86_64/media/main/release/lib64sasl2-2.1.25-4-mdv2012.0.x86_64.rpm

004

[root@iZm5e3vnh3gtu6fzpvc2ooZ ~]# systemctl restart mysql

Job for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details.
[root@iZm5e3vnh3gtu6fzpvc2ooZ ~]# more /var/lib/mysql/iZm5e3vnh3gtu6fzpvc2ooZ.err
2018-03-11 16:21:02 4452 [Note] Plugin ‘FEDERATED’ is disabled.
/usr/sbin/mysqld: Can’t find file: ‘./mysql/plugin.frm’ (errno: 13 – Permission denied)
2018-03-11 16:21:02 4452 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.
2018-03-11 16:21:02 4452 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-03-11 16:21:02 4452 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-11 16:21:02 4452 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-03-11 16:21:02 4452 [Note] InnoDB: Memory barrier is not used
2018-03-11 16:21:02 4452 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-11 16:21:02 4452 [Note] InnoDB: Using Linux native AIO
2018-03-11 16:21:02 4452 [Note] InnoDB: Using CPU crc32 instructions
2018-03-11 16:21:02 4452 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-03-11 16:21:02 4452 [Note] InnoDB: Completed initialization of buffer pool
2018-03-11 16:21:02 4452 [ERROR] InnoDB: ./ibdata1 can’t be opened in read-write mode
2018-03-11 16:21:02 4452 [ERROR] InnoDB: The system tablespace must be writable!
2018-03-11 16:21:02 4452 [ERROR] Plugin ‘InnoDB’ init function returned error.
2018-03-11 16:21:02 4452 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2018-03-11 16:21:02 4452 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-03-11 16:21:02 4452 [ERROR] Aborting
解决办法solution：
chown mysql.mysql -R /var/lib/mysql

……

阅读全文

Jenkins_library_err

2015年1月11日

| CI/CD Error

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17


Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.workflow.cps.CpsClosure2 getCode). 

### Administrators can decide whether to approve or reject this signature.
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.workflow.cps.CpsClosure2 getCode)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:270)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:160)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:143)
	at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:135)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
	at WorkflowScript.run(WorkflowScript:30)

进入jenkins的【系统管理】–>【脚本命令行】，然后你应该就会明白了。

……

阅读全文

分类 Error 中的文章

001

002

003

004