@Dashrender said in Snipe-IT Departmental Reporting:

@wirestyle22 said in Snipe-IT Departmental Reporting:

@Dashrender said in Snipe-IT Departmental Reporting:

@wirestyle22 said in Snipe-IT Departmental Reporting:

Got it to work. Edit the below file.

app/Console/Commands/LdapSync.php

Edit max_execution time and memory_limit

ini_set('max_execution_time', 1200); //600 seconds = 10 minutes ini_set('memory_limit', '1000M');

what was the default in those?

ini_set('max_execution_time', 600); //600 seconds = 10 minutes
ini_set('memory_limit', '500M');

Wow - so it took more than 10 or more than 500 M RAM to import all that - due to your numbers, I 'm guessing it was the RAM more than the time.

Not sure honestly--it took awhile. I spoke to a snipe-it Dev and they could sync 15k accounts with these settings. I needed this functionality so I can create a script to sync users every day at 1:00 AM.

@wrx7m I'm not sure. If all else fail, they do have chat room to let them know.
https://gitter.im/snipe/snipe-it

Just updated one client system. Now on v4.5.0 build 3701 (gbf1e742df)

@dustinb3403 said in Need some help with crontab:

Ok and that is what it was.

Simply needed to make a bash script out of it and have it scheduled to run, rather than using the commands directly in cron.

Problem solved.

Solution:

pwd /usr/bin/local touch expiring-alert.sh vi expiring-alert.sh /usr/bin/php /var/www/html/snipeit/artisan snipeit:expiring-alerts sudo vi /etc/crontab 35 * * * 1 <user> /usr/local/bin/expiring-alert.sh

Presumably changing this to be @daily or @weekly would work as well.

MOst of the time that is how I have it setup on my crontab, same for my certbot scripts too.

I also had to fix a permissions issue from a while back, that wasn't affecting anything until I went to get this feature to be functional.

@zachary715
You can turn on debug by changing false to true in .env file, so you can see more information instead of Whoops, looks like something went wrong.

# REQUIRED: BASIC APP SETTINGS # -------------------------------------------- APP_ENV=production APP_DEBUG=true APP_KEY= APP_URL= APP_TIMEZONE=America/Denver APP_LOCALE=en

@thwr said in Snipe-IT History lookup issue:

@dustinb3403 said in Snipe-IT History lookup issue:

Appears to be a cache issue.

Can see the info in an incognito window.

try a hard reload maybe

https://superuser.com/a/512833

Already resolved, but thanks

@black3dynamite said in Snipe-IT php upgrade.php install:

@dustinb3403 said in Snipe-IT php upgrade.php install:

No denials found.

100% done found 0 alerts in /var/log/audit/audit.log

Is apache the owner of snipeit directory, subdirectories, and files?

apache : apache owns at least storage, which is where those files are. (I am a part of this group)

@jaredbusch said in Snipe-IT updating from 4.1.3 with new Laravel Requirement:

[[email protected] ~]# cd /var/www/html/snipeit/ [[email protected] snipeit]# git pull

Doh.. yeah my update script does this.

I'm using a basic label printer and just printing off the asset tag. We also don't need anything special either. . . so.

@jaredbusch Thanks
Must of been a setting i was missing in my NGINX conf file. Made it too look more like yours and i'm working 🙂

@tiagom said in Error while installing Snipe IT:

@scottalanmiller said in Error while installing Snipe IT:

Snipe-IT has a lot of fragility around their install scripts, and not a huge user base so issues are difficult to track down.

I can personally promise that v4 installs under Debian 8 & 9.1, Ubuntu 14.04.5 & 16.04.3 & 17.04 and CentOS 6 & 7.

If it doesn't ping me.

And on Fedora with my pull request ( that I have to clean up and resubmit).

@aaronstuder hi I couldn't succeed that installation I reinstalled centos 7 1708 the same result someone can help? 0_1525526184662_image.png

I ran out of test time the other day, for Fedora 26. But it seemed to have worked for that part.

I had other issues.

I have not upgraded any of my systems to 4 yet. Glad to see my supposition was correct.

I started using the hosted version. One, because it was cheaper and two, because I needed something sooner than later and didn't have time to deploy and get it going. I confirmed that I can move the data out and host myself in the future.

I like it overall but some of the importing has proven to be flaky when grabbing csv files. Sometimes the header doesn't really apply and I will have to make a small adjustment and then reimport. I am still in the process of adding assets but I like it overall. I also use SpiceWorks reports and verify against known good data as I import the csvs.

@hobbit666 no this is just for the mysql database.

I've created a feature request on github as well, found here.