You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have pacmon running on 4 different machines which have Manjaro KDE 64 bit installed on them. The first big update of around 286 packages (700mb or so) came around so I did a full update on one machine then tried to update my two laptops assuming they'd go quickly through the update....instead they downloaded all the files as if pacmon wasn't even there. I verified via systemctl status pacmon that all were running and seeing each other. Example:
[famewolf@Asus_D510 log]$ systemctl status pacmon
● pacmon.service - pacmon
Loaded: loaded (/usr/lib/systemd/system/pacmon.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-06-20 00:17:32 EDT; 1 weeks 6 days ago
Main PID: 456 (pacmon)
Tasks: 11 (limit: 4567)
Memory: 7.1M
CGroup: /system.slice/pacmon.service
└─456 /usr/bin/pacmon
Regretfully I've pulled pacmon and I've switched over to pacserve since I was using mobile data at the time with the laptops and needed the 700mb in updates to apply. I can tell you when I initially started doing a yaourt update it was showing me that it was hitting against the local server prior to going out on the net. I had kept a VM with pacmon installed so I could test but in the process of doing the update I ran out of space in the VM and attempted to resize it larger...it corrupted the .vdi so now that vm won't boot and will require a re-install. I guess this can be closed.
I have pacmon running on 4 different machines which have Manjaro KDE 64 bit installed on them. The first big update of around 286 packages (700mb or so) came around so I did a full update on one machine then tried to update my two laptops assuming they'd go quickly through the update....instead they downloaded all the files as if pacmon wasn't even there. I verified via systemctl status pacmon that all were running and seeing each other. Example:
[famewolf@Asus_D510 log]$ systemctl status pacmon
● pacmon.service - pacmon
Loaded: loaded (/usr/lib/systemd/system/pacmon.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-06-20 00:17:32 EDT; 1 weeks 6 days ago
Main PID: 456 (pacmon)
Tasks: 11 (limit: 4567)
Memory: 7.1M
CGroup: /system.slice/pacmon.service
└─456 /usr/bin/pacmon
Jul 03 00:02:55 Asus_D510 pacmon[456]: /extra.db
Jul 03 00:02:55 Asus_D510 pacmon[456]: /community.db
Jul 03 00:02:55 Asus_D510 pacmon[456]: /multilib.db
Jul 03 00:23:27 Asus_D510 pacmon[456]: /core.db
Jul 03 00:23:28 Asus_D510 pacmon[456]: /extra.db
Jul 03 00:23:28 Asus_D510 pacmon[456]: /community.db
Jul 03 00:23:28 Asus_D510 pacmon[456]: /multilib.db
Jul 03 17:55:58 Asus_D510 pacmon[456]: Server found: http://192.168.3.112:41234
Jul 03 17:55:58 Asus_D510 pacmon[456]: Server found: http://192.168.3.237:41234
Jul 03 17:55:58 Asus_D510 pacmon[456]: Server found: http://192.168.3.252:41234
I'm unable to locate any kind of log. Any suggestions? I'm also uncertain why extra, community and multilib are showing up twice in the list above.
The text was updated successfully, but these errors were encountered: