Jump to content

ph4ckvv3r

Members
  • Posts

    28
  • Joined

  • Last visited

About ph4ckvv3r

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Ireland

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Peter, I was using 8.1.4 happily and it stopped working for no reason. So I've decided to update to 8.1.5, which then got me into the need to remove 8.1.4 and install 8.1.5 from zero, which installs it. Now the problem is that it installs but it has lots of errors. I don't think it is permissions as the service requires root to be installed and run, so... 😕 is there anything I can check here? Specific logs?
  2. Ok, solved the installation problem, but not the running. 8.1.5 is crashing on Ubuntu 21.
  3. Seems I've found the reason: 8.1.4 service was started but crashing, so no lock created. Since I was installing 8.1.5 on top of it, it was trying to find the lock but couldn't so... 🙂 One crash on top of another. Solved by removing eea before trying to install new version.
  4. Hi, I always keep my Ubuntu updated as much as possible, I can't use version 20.04 as it doesn't support my hardware, so I have to use 21. It was all working fine till this week, but an update from Ubuntu came and now I get a segmentation fault on 8.1.4. I then noticed that 8.1.5 is the latest, I've downloaded it and now I have a different errot message: $ sudo dpkg -i eea-8.1.5.0-ubuntu18.x86_64.deb (Reading database ... 272993 files and directories currently installed.) Preparing to unpack eea-8.1.5.0-ubuntu18.x86_64.deb ... Unpacking eea (8.1.5.0) over (8.1.4.0) ... Setting up eea (8.1.5.0) ... ESET Endpoint Antivirus Error: Cannot connect to Confd: No such device or address Only reference to someone who had this error before was never answered: https://forum.eset.com/topic/27816-errors-when-installing-on-debian/ There is a similar error here (just slightly different error message): https://forum.eset.com/topic/23121-efs-715580x86_64-confd-problem/ Any ideas on how to solve this problem?
  5. Hi, one last thing added to the exceptions list: /opt/eset. I was having this error, so I thought it would be better not to give access to my user to the antivirus folder and at the same time add it to the exclusions folder. I must report that I have no more slowness here.
  6. Hi guys, So after ALL those changes, I still had random moments of slowness which were solved by restart eea service. Then I thought: is this antivirus scanning the filesystem? So, does this mean that write and read from network device is being scanned too? Is it also scanning /proc?! I've decided to add /dev and /proc to the "ignored" paths (+ /var/lib/docker). If I notice that I don't have anymore hangs on Monday morning boots after machine down for 2 days, I will let you know.
  7. Wel, another thing I will try here: IntelliJ just warned about low values for inotify.max_user_watches. Changing it now to fs.inotify.max_user_watches=5242881 fs.inotify.max_user_instances=1024 fs.inotify.max_queued_events=32768 I still had one episode of slowness here. But most of the time machine is super usable. Let's hope those limits increased fix the problem.
  8. "apt fix broken install" did the trick, but the my machine is still really slow when RTP is on. Question: is anybody else out there using NVidia RTX 30 series with multiple displays? I have 3 screens here and I only notice the slowness when using X. If I boot to text, I'm ok.
  9. Hi, seems I was abandoned but I'm reporting another thing now... I've just upgraded my kernel to get 5.13, as I'm stuck on 5.11 with Ubuntu 21.04. And, I'm repeating the whole setup process again and for the first time I get this message of missing packages here So, now I will try to sort this out and see what happens.
  10. Hi all, I've found this checking my syslog. The first part seems a bit problematic, other 2 images seems just RTP hooking to the syscalls to do RTP. I've noticed that the Gnome Tracker is quite intensive on file scanning... Shouldn't be a problem but maybe at some point it could have a conflict on file access? Well, leaving this here, not sure this helps.
  11. LesRMed and Peter, Yesterday I couidn't even do screenshots anymore. I've captured, and when trying to paste images were broken and machine started to be really slow again. I ran htop and see my cores at very low usages (2-5%) and plenty of RAM - I have 64GB so it's quite hard to get it full. Today I've noticed slowness twice, and it was on the service restart I've put in cron (which, tbh, wasn't causing problems before). Slowness happened today at 11h15 and 12h00. The first one I had to reboot as I was doing a call that exact moment, but the second one at 12h00 I waited. 2 minutes. Machine comes back to normal. So, I've decided to comment the crontab restart in the service. And I will start to check if the slowness is only on boot as others have reported. in my case it happens "sometimes" on boot, but it had stopped for a while. Well, there you have date and time (13/08/2021, 11h15 and 12h00-12h02) AND MY LOGS! Ehhhhh! 😄 Maybe this will solve the mistery... BTW: I can't attach the .tar.gz from logs here. Hahahaha, it's funny, file has been generated by your tool. Here is the zipped version with my logs. Hope you can find something there. Cheers, Pablo eea_logs.zip
  12. Hi Peter, Does this help? On reboot some ESET messages. Missing part are timestamps on the left, no useful help there, I think. About LesRMed answer: software installs that part around with the FS access may leave some "scars" behind. So, superhot's system was normal, installed ESET, got b slower, remove and didn't help: so maybe there is also a problem on uninstalling it too. Are you going though the same problem as us? If not, you probably can't simulate the problem locally to understand the problem or help. I've mentioned it once and would like to mention it again, as there are other softwares that are incompatible with it: I use Nvidia's proprietary driver for X. Anybody who is having this issue is using the Nvidia proprietary driver too? I would not be surprised that this is the root of all this pain. Cheers, Peter and Superhot.
  13. SUPERHOT, so far my solution has been to have a cronjob to reestart eea service every 15 minutes. Sometimes the machine boots slow, I go for a cigarrete, coffe, bath, and when I'm back it's normal. It's really random problem, can't get a track of what is slowing down the machine. Amazing enough, running HTOP shows all my cores using less than 2%. But I can badly run something in terminal. All of the sudden (every 15 minutes) service is restarted, cores go really high and back to normal in seconds. Add this to /etc/crontab and that's the "fix" you can do at the moment. */15 * * * * root systemctl restart eea
×
×
  • Create New...