• hexo d 部署博客时出错


    问题描述:

      // 第一次遇到的问题
      Error: packet_write_wait: Connection to 192.30.253.113 port 22: Broken pipe
      packet_write_wait: Connection to 192.30.253.113 port 22: Broken pipe
      fatal: sha1 file '<stdout>' write error: Broken pipe
      fatal: The remote end hung up unexpectedly
      fatal: The remote end hung up unexpectedly
      FATAL Something's wrong. Maybe you can find the solution here: http://hexo.io/docs/troubleshooting.html
      Error: packet_write_wait: Connection to 192.30.253.113 port 22: Broken pipe
      fatal: sha1 file '<stdout>' write error: Broken pipe
      fatal: The remote end hung up unexpectedly
      fatal: The remote end hung up unexpectedly
    
          at ChildProcess.<anonymous> (D:log
    ode_moduleshexo-utillibspawn.js:37:17)
          at emitTwo (events.js:126:13)
          at ChildProcess.emit (events.js:214:7)
          at ChildProcess.cp.emit (D:log
    ode_modulescross-spawnlibenoent.js:40:29)
          at maybeClose (internal/child_process.js:925:16)
          at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
    
      // 第N次遇到的问题
      [master 852bb8c] Site updated: 2018-10-20 02:04:33
      67 files changed, 536 insertions(+), 536 deletions(-)
      Connection reset by 192.30.253.113 port 22
      fatal: sha1 file '<stdout>' write error: Broken pipe
      fatal: The remote end hung up unexpectedly
      fatal: The remote end hung up unexpectedly
      FATAL Something's wrong. Maybe you can find the solution here: http://hexo.io/docs/troubleshooting.html
      Error: Connection reset by 192.30.253.113 port 22
      fatal: sha1 file '<stdout>' write error: Broken pipe
      fatal: The remote end hung up unexpectedly
      fatal: The remote end hung up unexpectedly
    
          at ChildProcess.<anonymous> (D:log
    ode_moduleshexo-utillibspawn.js:37:17)
          at emitTwo (events.js:126:13)
          at ChildProcess.emit (events.js:214:7)
          at ChildProcess.cp.emit (D:log
    ode_modulescross-spawnlibenoent.js:40:29)
          at maybeClose (internal/child_process.js:925:16)
          at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
    

    解决方法:

    往 Github push 文件时出现 packet_write_wait: Connection to 192.30.253.112: Broken pipe 这个问题是因为传输
    过程被打断,而导致传输失败。

    1、尝试过 ssh -o ServerAliveInterval=60 mzwua@192.30.253.112(只有一次有效,后面再遇到就挂了!)

    2、有网友说:删除.deploy_git文件后重新部署(我试了一下还是挂了!)

    3、改用手机热点(竟然可以了,Why??防火墙??)

  • 相关阅读:
    完全备份、差异备份以及增量备份的区别(转)
    Backup Exec Inventory 与Catalog的含义(转载)
    从客户端中检测到有潜在危险的Request.Form值的解决办法
    IQueryable与IEnumberable的区别(转)
    SQL递归查询(with cte as) 物料分解
    Http权威指南笔记(二) Http状态码大全
    Http权威指南笔记(一) URI URL URN 关系
    echarts在.Net中使用实例(二) 使用ajax动态加载数据
    echarts在.Net中使用实例(一) 简单的Demo
    sql显示12个月数据
  • 原文地址:https://www.cnblogs.com/wumz/p/9820295.html
Copyright © 2020-2023  润新知