dragos_kai's questions

所以，就脚本而言，我是一个完全的新手，就像这是我的第一个。我创建了以下脚本：

# This simply declares which states we are using to create tarballs from
for blah in ar ky ms ny; 
do 
    # This will go into each tomcat-state directory and create a tarball in /home/ec-user for all files older than 90 days
    find /var/www/apps/tomcat-${blah}/logs -type f -mtime +90 | xargs tar -cvzf /home/ec2-user/archive-${blah}.tar.gz; 

    # This creates a master archive tarball containing all the archive-state.tar.gz files
    tar -cvzf /home/ec2-user/ebd-log-archives.tar.gz /home/ec2-user/archive-${blah}.tar;

    # Since in step one, we archives all files older than 90 days, this step removes them.
    # find /var/www/apps/tomcat-${blah}/logs -type f  -mtime +90 -exec rm {} \;

    # And since we have the master archive file, this removes the archive-state files
    rm /home/ec2-user/archive-${blah}.tar.gz;
done

我已经注释掉删除日志以进行测试。

问题是，当我得到 master tarball 时，里面只有 NY，或者我把哪个放在循环中的最后一个（我测试了这个以确保它不仅仅是一个奇怪的 NY 东西）

不确定发生了什么，我在该服务器上的措辞上针对与此类似的旧脚本进行了测试，并且该脚本运行良好。

编辑：感谢您的回复，我已将脚本更新为：

# This creates the master tarball we will be using
tar -cvzf /home/ec2-user/ebd-log-archives.tar.gz

# This simply declares which states we are using to create tarballs from
for blah in ar ky ms ny; 
do 
    # This will go into each tomcat-state directory and create a tarball in /home/ec-user for all files older than 90 days
    find /var/www/apps/tomcat-${blah}/logs -type f -mtime +90 | xargs tar -cvzf /home/ec2-user/archive-${blah}.tar.gz; 

    # This creates a master archive tarball containing all the archive-state.tar.gz files
    tar -rvzf /home/ec2-user/ebd-log-archives.tar.gz /home/ec2-user/archive-${blah}.tar;

    # Since in step one, we archives all files older than 90 days, this step removes them.
    # find /var/www/apps/tomcat-${blah}/logs -type f  -mtime +90 -exec rm {} \;

    # And since we have the master archive file, this removes the archive-state files
    rm /home/ec2-user/archive-${blah}.tar.gz;
done

我会尝试运行这个并发布更新

大家好，我正在尝试使用https://obsproject.com/forum/resources/how-to-set-up-your-own-private-rtmp-server-using-中的说明设置新的 RTMP 服务器nginx.50/并且我遇到了 Facebook Live 的问题。我有一种感觉，这归结为他们新的只接受 SSL 连接

弃用 对 RTMP 服务器 URL 的支持将被弃用，从 5 月 1 日起将不再支持非安全 URL。请确认您的编码器支持 RTMPS，并更新编码器设置以插入新的安全服务器 URL 以便继续。

所以我遇到了我尝试停止并启动 nginx 的问题，并将其作为配置的底部：

rtmp {  
        server {
                listen 1935;
                listen 443;
                chunk_size 4096;

                application live {
                        live on;
                        record off;
                        push 'rtmps://live-api-s.facebook.com:443/rtmp/insertedmykeyhere';

                }
        }
}

我正进入（状态：

root@localhost:/usr/local/nginx/conf# sudo /usr/local/nginx/sbin/nginx -s stop nginx: [emerg] 无效端口在 url "rtmps://live-api-s.facebook.com :443/rtmp/218

我不能用它做任何其他事情。当我评论 facebook 时，我可以毫无问题地流式传输到 Twitch、Mixer、YouTube 等，但这阻碍了我。