司马他 | Codes Speak Louder than Words.

Windows安装Curl工具

- 2018年06月13日

Windows下排查问题常需要curl进行请求访问，下面记录一下windows安装curl过程：

1、https://curl.haxx.se/download.html#Win64 进行下载

2、新建目录，如C:\curl，将所下载内容解压

3、配置环境变量path，计算机右键->属性->高级系统设置->高级->环境变量->path，进行修改新增;C:\curl

解决WordPress后台登录后报File_not_found问题

- 2018年06月13日

wordpress 的后台，一些菜单标题都是相对路径，这样通过访问 www.xxx.us/wp-admin 再点击菜单比如写文章功能，会跳转到 www.xxx.us/post-new.php ，而我们想要的是跳转到 www.xxx.us/wp-admin/post-new.php 这个地址，否则将是会报File not Found

解决方案：

如果用户输入了 www.xxx.us/wp-admin 我们强制加上/ 变成 www.xxx.us/wp-admin/

需要再nginx配置文件中增加配置：

rewrite /wp-adminscheme:// $host$ uri/ permanent;

以上即可~

Windows安装Composer选择php.exe报错问题

- 2018年06月11日

环境重装，重新安装一把composer，但是选择php7之后版本报错，本地环境不用php7是绝对不行的…

The PHP exe file you specified did not run correctly:
C:\phpStudy\PHPTutorial\php\php-7.2.1-nts\php.exe

The program failed to run correctly. Try reinstalling the program to fix this problem. Make sure you have installed the appropriate Visual C++ Redistributable.

确定问题，缺少VC14，下载安装之后再安装composer即解决

下载地址：http://www.xdowns.com/soft/184/dll/2016/Soft_164980.html

记得安装完之后重启一下cmd，否则composer命令无法再当前cmd中执行

詹姆斯不会有决定三

- 2018年06月10日

总决赛过去了，勇士实力强劲，实至名归。

詹姆斯这个赛季有点悲情色彩，绝对力量是值得尊敬的，每个人都羡慕这种绝对力量，也都希望拥有，得分场均34分，近三双的数据，非常强劲的控制力，最近复联大热，大家给了他一个灭霸的称号。

灭霸詹最终是落败了，篮球就是这个规则，靠的是团队，骑士败了，但是詹姆斯并不是失败者，他的表现早已是个winner。

不过大家开始讨论是否会上演决定三？

我觉得不会，首先

1、克利夫兰是詹姆斯的家，NBA球员大部分都会想在最初的地方

2、决定一成本很大的，球迷都是不理性的，回到骑士拿到冠军好歹追回来一点

3、把家乡球队骑士变得强大吧，换个教练，锻炼好新人

不过写到这里，好担心骑士管理层，毕竟外面诱惑还是很多的，比如我们大马刺…

音乐剧-千万留神

- 2018年06月10日

千万留神

讲述的是一个因言语冲突致人轻伤坐牢15年的人，出狱后成为一个演员的一些事情

其中桑医生劝他的一段特别有意思，你要强大，要适应，要改变，不要冲动，不要盲目

可惜没有版权的在线音乐…

《人是鱼变的》歌词：
我们总要
随着社会改变
去强大自己
然后再去
改变世界
哪能万事顺着你
我们必须
适应世界
最终百毒都不侵
然后才能
活在世上
笑看污染满天飞

Fabric 错误异常处理

- 2018年06月05日

Fabric是Python编写的自动化运维工具，使用fabric批量去机器上面执行shell脚本的时候，可能会遇到机器故障等情况，造成执行中断，那么能否忽略或者说爆出异常之后继续执行呢？那就需要fabric的异常处理，具体实现参见下面

import logging

try:
    1/0
except Exception as e:
    logging.exception(e)

错误异常打印如下：

ERROR:root:division by zero
Traceback (most recent call last):
  File "/home/padraic/Dropbox/python/py3/size.py", line 105, in <module>
    1/0
ZeroDivisionError: division by zero

Process finished with exit code 0

《一分钟经理人》读书笔记

- 2018年04月25日

一分钟经理人这本书比较薄，上下班通勤路上就看完了，包含内容归纳的也比较简洁，印象比较深的是其中一页插图，分别对应着开始时要考虑一分钟目标、成功时要考虑一分钟表扬和失败时应考虑一分钟更正，简洁但不简单，又看了一下Kindle上阅读时的标注，回顾一下书上的内容。
Read more

dependencies.dependency.version missing问题解决

- 2018年01月26日

Spring Boot打算引入Redis但是导入依赖包之后却报如下错误

        <dependency>
          <groupId>org.springframework.boot</groupId>
          <artifactId>spring-boot-starter-redis</artifactId>
        </dependency>

Project build error: 'dependencies.dependency.version' for org.springframework.boot:spring-boot-starter-redis:jar is missing.

同时pom配置文件中位置，报如下位置：

    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>1.5.9.RELEASE</version>
        <relativePath/> <!-- lookup parent from repository -->
    </parent>

Multiple annotations found at this line:
    - For artifact {org.springframework.boot:spring-boot-starter-redis:null:jar}: The version cannot be empty. (org.apache.maven.plugins:maven-resources-plugin:2.6:testResources:default-
     testResources:process-test-resources) org.apache.maven.artifact.InvalidArtifactRTException: For artifact {org.springframework.boot:spring-boot-starter-redis:null:jar}: The version cannot be empty. at 
     org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:148) at org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123) at 
     org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:157) at 
     org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:57) at 
     org.apache.maven.project.artifact.MavenMetadataSource.createDependencyArtifact(MavenMetadataSource.java:328) at 
     org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:503) at 
     org.apache.maven.lifecycle.internal.DefaultProjectArtifactFactory.createArtifacts(DefaultProjectArtifactFactory.java:50) at 
     org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:119) at 
     org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:330) at 
     org.eclipse.m2e.core.internal.embedder.MavenImpl $11.call(MavenImpl.java:1362) at org.eclipse.m2e.core.internal.embedder.MavenImpl$ 11.call(MavenImpl.java:1) at 
     org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at 
     org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360) at 
     org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52) at 
     org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137) at org.eclipse.m2e.core.internal.builder.MavenBuilder $1.method(MavenBuilder.java:172) at org.eclipse.m2e.core.internal.builder.MavenBuilder$ 1.method(MavenBuilder.java:1) at org.eclipse.m2e.core.internal.builder.MavenBuilder $BuildMethod$ 1 $1.call(MavenBuilder.java:115) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.builder.MavenBuilder$ BuildMethod $1.call(MavenBuilder.java: 105) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.builder.MavenBuilder$ BuildMethod.execute(MavenBuilder.java:
     86) at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200) at org.eclipse.core.internal.events.BuildManager $2.run(BuildManager.java:734) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) at org.eclipse.core.internal.events.BuildManager$ 1.run(BuildManager.java:300) at 
     org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) at 
     org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) at 
     org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at 
     org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    - For artifact {org.springframework.boot:spring-boot-starter-redis:null:jar}: The version cannot be empty. (org.apache.maven.plugins:maven-resources-plugin:2.6:resources:default-
     resources:process-resources) org.apache.maven.artifact.InvalidArtifactRTException: For artifact {org.springframework.boot:spring-boot-starter-redis:null:jar}: The version cannot be empty. at 
     org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:148) at org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123) at 
     org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultArtifactFactory.java:157) at 
     org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact(DefaultArtifactFactory.java:57) at 
     org.apache.maven.project.artifact.MavenMetadataSource.createDependencyArtifact(MavenMetadataSource.java:328) at 
     org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:503) at 
     org.apache.maven.lifecycle.internal.DefaultProjectArtifactFactory.createArtifacts(DefaultProjectArtifactFactory.java:50) at 
     org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:119) at 
     org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:330) at 
     org.eclipse.m2e.core.internal.embedder.MavenImpl $11.call(MavenImpl.java:1362) at org.eclipse.m2e.core.internal.embedder.MavenImpl$ 11.call(MavenImpl.java:1) at 
     org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at 
     org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360) at 
     org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52) at 
     org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137) at org.eclipse.m2e.core.internal.builder.MavenBuilder $1.method(MavenBuilder.java:172) at org.eclipse.m2e.core.internal.builder.MavenBuilder$ 1.method(MavenBuilder.java:1) at org.eclipse.m2e.core.internal.builder.MavenBuilder $BuildMethod$ 1 $1.call(MavenBuilder.java:115) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112) at org.eclipse.m2e.core.internal.builder.MavenBuilder$ BuildMethod $1.call(MavenBuilder.java: 105) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.builder.MavenBuilder$ BuildMethod.execute(MavenBuilder.java:
     86) at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200) at org.eclipse.core.internal.events.BuildManager $2.run(BuildManager.java:734) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) at org.eclipse.core.internal.events.BuildManager$ 1.run(BuildManager.java:300) at 
     org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) at 
     org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) at 
     org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at 
     org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

解决方案

排查一：

是否引入了<parent>标签，如果未引入请引入，或者主动加上version

排查二：

是否dependences包含在了dependencyManagement标签内

排查三：

其中网上搜索了一下很多答案集中在是否引入了parent，但是parent是完整引入的，最终发现原来是因为使用的Spring Boot 1.5，而Spring Boot 1.2之后不再支持spring-boot-starter-redis，更换之后就OK了，至于这两个有何不一致，没什么不一致，为何名称变了，大概可能是为了统一，记录一下，如果遇到的小伙伴麻烦检查一下，是否将 spring-boot-starter-data-redis 写成了spring-boot-starter-redis 。

解决Error: pg_config executable not found问题

- 2018年01月22日

最近安装sentry时，需要安装postgresql，但是安装过程中报如下问题

Error: pg_config executable not found.

最终查看pg_config是存在的

sudo find / -name "pg_config" -print

但是path里面没有，直接导入pa_home中bin目录的所有命令解决

export PG_HOME=/usr/pgsql-9.6
export PATH= $PATH:$ PG_HOME/bin

解决SOAP客户端在请求https时设置超时时间无效导致进程卡死问题

- 2018年01月22日

目前有一个进程服务脚本是不断查询渠道的接口，但是历史问题是有时订单量大的时候进程会卡死，这次遇到了进行排查一下：

首先获取该进程ID

ps -aux | grep QueryABC.php

sync360  11115  0.0  0.0   6564   864 ?        Ss   14:00   0:00 /bin/sh -c /usr/local/bin/php /xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/QueryABC.php BILL99DF 10-8>> /home
sync360  11124  0.0  0.4 361628 17296 ?        S    14:00   0:04 /usr/local/bin/php /xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/QueryABC.php BILL99DF 10-8
sync360  25230  0.0  0.0  63384   872 pts/0    S+   15:28   0:00 grep QueryABC.php

strace查看该进程正在持续的状态

sudo strace -T -tt -e trace=all -p 11124
[sudo] password for ancongcong: 
Process 11124 attached - interrupt to quit
15:33:07.259044 read(9,

lsof查看进程的所使用的文件

lsof -p 11124

....
php     11124 sync360  mem    REG        8,1    23736    3211320 /lib64/libnss_dns-2.5.so
php     11124 sync360    0r  FIFO        0,6          1522728709 pipe
php     11124 sync360    1w   REG        8,1  4088819    1869737 /xxxx/xxxx/xxxx/xxxx/logs/QueryABC.log
php     11124 sync360    2w  FIFO        0,6          1522728710 pipe
php     11124 sync360    3w   CHR        1,3                 982 /dev/null
php     11124 sync360    4u  IPv4 1522728838                 TCP 211.151.122.234:46004->10.117.128.47:rtmp-port (CLOSE_WAIT)
php     11124 sync360    5wW  REG        8,1        0    2704363 /xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/lockfile/QueryABC.php.BILL99DF.10-8
php     11124 sync360    6u  IPv4 1522728841                 TCP 211.151.122.234:51019->10.117.128.46:rtmp-port (CLOSE_WAIT)
php     11124 sync360    7w   REG        8,1 31960384    1869789 /xxxx/xxxx/xxxx/xxxx/logs/XXXX_info.log.20180118
php     11124 sync360    8w   REG        8,1 18151722    1869806 /xxxx/xxxx/xxxx/xxxx/logs/XXXX_QRY_info.log.20180118
php     11124 sync360    9u  IPv4 1522729884                 TCP 211.151.122.234:54976->61.152.114.130:https (ESTABLISHED)

sudo netstat -tunpa | grep 11124
tcp        0      0 211.151.122.234:54976       61.152.114.130:443          ESTABLISHED 11124/php           
tcp        1      0 211.151.122.234:51019       10.117.128.46:3500          CLOSE_WAIT  11124/php           
tcp        1      0 211.151.122.234:46004       10.117.128.47:3500          CLOSE_WAIT  11124/php

可以发现最终是停留在https的链接建立，等待获取数据，查看此处代码

ini_set('default_socket_timeout',30);
 $scOptions = array('connection_timeout' => 30);$ clientObj = new SoapClient(  $wsdl ,$ scOptions);

当前版本php较老，这里是有个bug的在https链接请求时SOAPClient的超时时间是不生效，最终采取如下方案解决此问题：

复写SOAPClient，在https时候使用curl来完成请求解决问题

<?php
class SoapClientTimeout extends SoapClient
{
    private  $timeout; public function __setTimeout($ timeout)
    {
        if (!is_int( $timeout) && !is_null($ timeout))
        {
            throw new Exception("Invalid timeout value");
        }

         $this->timeout =$ timeout;
    }

    public function __doRequest( $request,$ location,  $action,$ version,  $one_way = FALSE) { if (!$ this->timeout)
        {
            // Call via parent because we require no timeout
             $response = parent::__doRequest($ request,  $location,$ action,  $version,$ one_way);
        }
        else
        {
            // Call via Curl and use the timeout
             $curl = curl_init($ location);

            curl_setopt( $curl, CURLOPT_VERBOSE, FALSE); curl_setopt($ curl, CURLOPT_RETURNTRANSFER, TRUE);
            curl_setopt( $curl, CURLOPT_POST, TRUE); curl_setopt($ curl, CURLOPT_POSTFIELDS,  $request); curl_setopt($ curl, CURLOPT_HEADER, FALSE);
            curl_setopt( $curl, CURLOPT_HTTPHEADER, array("Content-Type: text/xml")); curl_setopt($ curl, CURLOPT_TIMEOUT,  $this->timeout);$ response = curl_exec( $curl); if (curl_errno($ curl))
            {
                throw new Exception(curl_error( $curl)); } curl_close($ curl);
        }

        // Return?
        if (! $one_way) { return ($ response);
        }
    }
}