1

sed '1,10d' file                   

1
2
3

sed ':label;N;s/\n//;b label' 

sed ':a;N;$!ba;s/\n//g' /root/.ssh/authorized_keys

 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

 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!