发表文章

[Ruby] 安装问题 RP3 Install issues RP3[maverick]

lucidwan 2017-10-9 30

不知道如何报告这一点, 图这是一个好地方作为任何。
我花了大约一个星期的时间来安装 Pi3 和 Odroid XU4。

以下是问题:
图像在两者上都写得很好。两个靴子都很好
PI (2 和3实际上)-解决方案-不要首先使用更新。在我的情况下, 我建立了 wifi, 然后 wman0 和 wap0, 在 localconf 运行特立独行的配置, 和一切更新正确。

如果你通过 "特立独行的更新第一次" 后, 它打破了系统-显然, 因为我们把多个新的东西和变化。问题是, 当您运行 "特立独行配置" 它的错误。
第一个错误是无效的类 "nginx"。 "模块" 文件夹中有一个用于 Nginx 的空文件夹。
这是很简单的, 一旦我想通了木偶和清单, 和安装路径的模块使用木偶。
nginx 的问题是, 它不会安装正确的依赖性-从傀儡, 我可以找到使用傀儡-nginx 和 jfryman-nginx。Jfryman 抛出一个服务器:: 资源错误。安装傀儡-nginx-强制修复它 (将声明添加到。
因此, 当你特立独行的配置, 它抛出了一吨的依赖性错误。
我正在运行的罚款 atm-不使用更新。我会测试一下

我会寄一个单独的给 Odroid。

原文:

Not sure how to report this, figure this is good a place as any.
I've spent a about a week messing with getting install on Pi3 and Odroid XU4.

Here are the issues:
Image writes fine on both. Both boot fine.
PI (2 and 3 actually)-Solution - don't use self-update first. In my case, I setup up wifi, then wman0 and wap0, in localconf- ran maverick configure, and everything updated correctly.

If you go through 'maverick self-update first' after boot it breaks the system - obviously since we're putting multiple new things and changes in. The problem is, that when you run 'maverick configure' it errors.
The first error is invalid class "nginx". The modules folder has an empty folder for Nginx.
This was simple enough to figure out once I figured out puppet and manifests, and the install path for modules using puppet.
The issue with nginx is that it won't install the correct dependencies - from puppet, that I could find using puppet-nginx and jfryman-nginx. Jfryman throws a server::resource error. Installing puppet-nginx --force fixes it (adds the declaration to the .conf)
So when you maverick configure, it throws out a ton of dependency errors.
I'm running fine - atm - without using self-update. I'll test this in a little bit.

I'll post a separate one for Odroid.

相关推荐
最新评论 (19)
fnoop 2017-10-9
1

真对不起, 这是一个愚蠢的意外提交的开发分支, 而我的大脑仍然在度假。 我现在就去修, 希望今晚。

原文:

Yup really sorry that was a stupid accidental commit of the dev branch while my brain was still on holiday. I'm just fixing that now, hopefully this evening.

fnoop 2017-10-9
2

傀儡 nginx 依赖关系现在是固定的:
voxpupuli/puppet-nginx#1107

我搞砸了模块提交。

原文:

puppet-nginx dependencies are now fixed btw:
voxpupuli/puppet-nginx#1107

I screwed up the module commit.

fnoop 2017-10-9
3

请您尝试:

maverick self-update
maverick configure

看看这些错误是否消失了?

原文:

Could you please try:

maverick self-update
maverick configure

And see if the errors are gone?

lucidwan 2017-10-9
4

谢谢!对不起, 我没有搜索它, 只是想得到它在那里, 而它是在我的脑海新鲜。

原文:

Thanks! Sorry I didn't search it, just wanted to get it out there while it was fresh on my mind.

lucidwan 2017-10-9
5

我会的!马上通知你

原文:

I will! Let you know soon.

lucidwan 2017-10-9
6

还行:
错误: 计算错误: 评估资源语句时出错, 计算错误: 计算资源语句时出错, 重复声明: Service_wrapper [hostapd] 已在文件/srv/标新立异/软件/特立独行/清单中声明/特立独行-模块/maverick_network/清单/init. pp: 270;无法声明 at/srv/特立独行/软件/特立独行/清单/特立独行-模块/maverick_network/舱单/interface_ap. pp:38 at/srv/特立独行/软件/特立独行/舱单/特立独行-模块/maverick_network/清单/interface_ap. pp: 38:5 at/srv/特立独行/软件/特立独行/清单/特立独行-模块/maverick_network/清单/process_interface. pp:62 在节点上特立独行-覆盆子. 首页

直接发生在 oncevcsrepo git 函数之后

原文:

Ok:
Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Service_wrapper[hostapd] is already declared in file /srv/maverick/software/maverick/manifests/maverick-modules/maverick_network/manifests/init.pp:270; cannot redeclare at /srv/maverick/software/maverick/manifests/maverick-modules/maverick_network/manifests/interface_ap.pp:38 at /srv/maverick/software/maverick/manifests/maverick-modules/maverick_network/manifests/interface_ap.pp:38:5 at /srv/maverick/software/maverick/manifests/maverick-modules/maverick_network/manifests/process_interface.pp:62 on node maverick-raspberry.home

happened directly after oncevcsrepo git function

fnoop 2017-10-9
7

啊. 这应该是一个修复:
#538

它应该禁用 hostapd, 如果它没有检测到 AP 接口定义, 它在广泛的测试期间工作正常, 但很明显, 它的某个地方仍然有一个 bug。 谢谢, wilil 重新:(

原文:

Aargh. This was supposed to be a fix for this:
#538

It's supposed to disable hostapd if it doesn't detect an AP interface definition and it worked fine during extensive testing, but obviously there's still a bug in it somewhere. Thanks, wilil reopen :(

lucidwan 2017-10-9
8

一切都好我去挖点

你是说这个函数是当它不检测和 AP?
我有一个 AP 接口定义和工作这一个。

原文:

It's all good. I'll do some digging in a bit.

Are you saying this function is for when it doesn't detect and AP?
I have an AP interface defined and working on this one.

fnoop 2017-10-9
9

是的, 在这里:
https://github.com/fnoop/maverick/blob/stable/manifests/maverick-modules/maverick_network/manifests/init.pp#L269

这个想法是, 如果它没有检测到 AP 类已经被调用 (定义), 然后它停止 hostapd, 否则它会干扰正常的接口操作。 但是木偶对于检测一个类是否可靠的定义有点滑稽, 我认为这是一个非确定性的排序问题。

原文:

Yes, it's here:
https://github.com/fnoop/maverick/blob/stable/manifests/maverick-modules/maverick_network/manifests/init.pp#L269

The idea is that if it doesn't detect that AP class has been called (defined) then it stops hostapd, as otherwise it interferes with normal interface operation. But puppet is a bit funny about detecting whether a class has been defined reliably, I think it's a non-deterministic ordering thing..

fnoop 2017-10-9
10

您可以尝试更新并重新配置吗? 我做了一个非常小的更新, 可能会或可能没有任何效果。

原文:

Could you try self-update and configure again? I made a very small update that may or may not have any effect..

lucidwan 2017-10-9
11

同样的错误, 这一次, 只是在 init 的行更改. pp: 268

原文:

Same error this time, just a line change in init.pp:268

fnoop 2017-10-9
12

好了, 这应该是固定的了。 你能测试一下吗?

原文:

OK this should be fixed now. Could you please test?

lucidwan 2017-10-9
13

很抱歉耽误了时间, 忙了一周。

它似乎要经过大多数的配置-直到它在 nginx 部分中给出了附加图像中的错误。这显然有 Grafana/MavCesium 没有工作@localhost: 6790 显示以下内容 (当然我没有做链接):

{{警报. 标题}}
文档
支持计划
社会
Grafana v4.3.2 (提交: ed4d170)
新版本可用!

Wifi 工作, 有 eth0, wlan0 和 wap0 工作后的配置-所以这是固定的:)

mavconf

原文:

Ok sorry for the delay, had a crazy-busy week.

It appears to go through the majority of the configure - until the nginx portion in which it gives the errors in the attached image. This obviously has Grafana / MavCesium not working @localhost:6790 shows the following (I didn't make the links of course):

{{alert.title}}
Docs
Support Plans
Community
Grafana v4.3.2 (commit: ed4d170)
New version available!

Wifi Works, have eth0, wlan0 and wap0 working after the config - so that's fixed : )

mavconf

fnoop 2017-10-9
14

@lucidwan谢谢你的更新。 我真的需要更新的文档-我倾向于这样做, 一旦我已经敲定了一个版本-但 grafana 已经在反向代理现在。 如果您只是转到浏览器 (默认端口 80), 则应该看到指向 Grafana 的链接。 我已经完全忘记了 mavcesium 在6790端口!(但令人高兴的是, 现在应该再次工作)。
对于 nginx 错误, 请为运行附加配置日志文件。 你应该找到它在〜/var/日志/特立独行。
编辑: 啊, 当然, 你不能访问端口 80, 直到你有 nginx 排序!

原文:

@lucidwan Thanks for the update. I really need to update the docs - I tend to do that once I've finalised a release - but grafana has moved behind a reverse proxy now. If you just go to in a browser (on the default port 80), you should see a link to Grafana. And I had totally forgotten about mavcesium on port 6790! (But happily that should work again now).
For the nginx error, could you please attach the configure log file for the run? You should find it in ~/var/log/maverick.
Edit: Ah of course you can't access port 80 until you've got nginx sorted!

lucidwan 2017-10-9
15

还行:

昨晚累了, 但在我退出之前, 我重新启动, 重新配置后, 我改变了一些 mavproxy 设置-它运行没有错误。
端口80和仪表板工作, 但。没有 Mavcesium

日志已附加。我包括 several-in 案

现在, 我只需要解决实际得到它连接到我的 FC:) 似乎无法得到它的工作自动取款机。
我需要从直升机上给它供电, 而不是我在想。可能是通讯上的地面参考问题

顺便-我很感激你的帮助和工作。Linux 远非我最喜欢的安装程序。我是一个黑客, 知道足够的危险。
我可以。。但我不是整个的粉丝-让我们做 cli 和命令最长的事情不断进程。拥有所有这些都是一件美好的事情。如果你需要检查 (一旦我得到它的设置和沟通), 我会帮助你随时问。

编辑: 我实际上是在沟通-微型飞行器 screen.log 显示它, 我只是不接 UDP 从 MP。有什么建议吗?

LBMaverickLogs 邮编

原文:

Ok:

Was tired last night, but before I quit I rebooted, re-ran the config after I changed some mavproxy settings - and it ran without error.
Port 80 and Dashboards working though. No Mavcesium.

Log is attached. I included several - in case.

Now I just have to sort out actually getting it to connect to my FC : ) Can't seem to get it working atm.
I need to power it from the copter instead I'm thinking. Probably a ground reference problem on the comms.

BTW - I appreciate the help and the work. Linux is far from my favorite thing to setup. I'm a hack and know enough to be dangerous..
I can..but I'm just not of fan of the whole -let's make the cli and commands the longest things ever- process. Having all of this available is a beautiful thing. I'm down to help if you need things checked (once I get it setup and communicating) Feel free to ask.

Edit: I'm actually communicating - the Mav screen.log show it, I'm just not picking up UDP from MP. Any suggestions?

LBMaverickLogs.zip

lucidwan 2017-10-9
16

联系上了最后尝试了所有 UDP 和创伤14573连接。

原文:

Got it connected. Finally tried all UDP and wound up 14573 connects.

fnoop 2017-10-9
17

好吧, 你有同样的 nginx 错误, 我做了, 和我一样, 它的工作第二次。 引发的问题:
#575

原文:

OK you got the same nginx error I did, and like me it worked the second time. Raised issue:
#575

fnoop 2017-10-9
18

你得到相同的 grafana wget 执行每次运行时, 我有时得到:
#574

原文:

You're getting the same grafana wget executing every run as I sometimes get:
#574

fnoop 2017-10-9
19

nginx 错误固定, grafana wget 只是一个烦恼, 并在它自己的问题跟踪。

很高兴你喜欢它到目前为止, 它的整个点是让你的生活更容易:)

原文:

nginx error fixed, grafana wget is just an annoyance and being tracked in it's own issue.

Glad you like it so far, whole point of it is to make life easier for you :)

返回
发表文章
lucidwan
文章数
1
评论数
8
注册排名
60717