@x23piracy I don’t think it’s worth the trouble or dev cycles.

@sudburr said:

Aside from doing it manually, it would be nice if you could download into a local repository/cache then locally swap by selecting internet delivered or locally cached; instead of relying on the internet all the time.

Perhaps… Figure out a way to just download all of the available kernels and inits… official and non official, old and new…

Just a big fat “download everything” button.

and a radio button for the source to use when you swap out kernels?

@matthew-wyneken Are you using the right address for the fog server during installation? Can you do a curl or wget of the certificate using Terminal on the MacOS system?

@Bigredcherokee re-run the installer and see if it comes back.

@x23piracy

• Reboot after install
• Shutdown after install
• Only install

r3566 fixes this bug. Just confirmed.

That’s how fast @Tom-Elliott works, to all of you who are skeptical of FOG Trunk.

@ch3i Not yet, thank you for reminding me. I’ll try to do it today. I actually need to.

@Lesso Nice article.

Feel free to request access to the FOG Project’s WiKi. We need more people that are good technical writers.

@avaryan said in Please Add an Option to Change the Default Page After Logon:

I set an Access Control rule to block access to the home node. It did take the icon away, but still took the user to that page at login.

This is humorous I have to ping @Fernando-Gietz about this one.

If you can enable remote access on MySQL, you can use a windows based utility like HeidiSQL to connect to the FOG database and just copy/paste your hosts. Alternatively, if you’re willing, you could use phpMyAdmin to do the same thing, but that’s a little harder to setup.

This might help with enabling remote access:
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL
http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html

How about having the installer move any existing file to /etc/exports.old ?

I love how this guy comes here - posts, gets impatient, posts again - then never comes back… and after he leaves, he gets 5 genuine pieces of advice from 5 different people - but he’ll never know that, will he?

All of us here have Jobs man! We are volunteers for the FOG Project!

Bumping this, it’s a good idea still.

@ch3i said:

@Wayne-Workman said:

https://wiki.fogproject.org/wiki/index.php/Fedora_21_Server

Seriously, the solution is to change OS ? XD

That’s my solution.

If the goal is to have a working FOG server, and the quickest route to that goal is a different OS, then yes, absolutely.

@ch3i Trying it now.

Are you using a consumer grade router? If so - what brand and model?

@lee-rowlett I see what your saying, and we should be able to associate multiple CIDRs for a node.

I’ve been looking at the database layout for locations and I’ve figured out how to do this. We add a CIDR field and add it to the composite primary key for the location table. This allows for a single storage node to have multiple locations associated with it - as long as each one has a different CIDR. Here’s my changes:

CREATE TABLE `location` (
       `lID` int(11) NOT NULL AUTO_INCREMENT,
       `lName` varchar(255) NOT NULL,
       `lDesc` longtext NOT NULL,
       `lStorageGroupID` int(11) NOT NULL,
       `lStorageNodeID` int(11) NOT NULL,
       `lCidr` varchar(50),
       `lCreatedBy` varchar(40) NOT NULL,
       `lCreatedTime` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
       `lTftpEnabled` enum('0','1') NOT NULL,
       PRIMARY KEY (`lID`),
       UNIQUE KEY `index0` (`lID`),
       UNIQUE KEY `index1` (`lName`),
       UNIQUE KEY `index2` (`lStorageGroupID`,`lStorageNodeID`,`lCidr`)
     ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC;

As you can see, there’s the new field lCidr that is optional. I’ve also added lCidr to the composite primary key. Next, I inserted some data:

insert into location(lName,lDesc,lStorageGroupID,lStorageNodeID,lCidr,lCreatedBy,lCreatedTime,lTftpEnabled) VALUES ('Floor2','None','1','1','10.0.1.0/24','wayne','2017-12-31 15:07:51','1');
insert into location(lName,lDesc,lStorageGroupID,lStorageNodeID,lCidr,lCreatedBy,lCreatedTime,lTftpEnabled) VALUES ('Floor1','None','1','1','10.0.2.0/24','wayne','2017-12-31 15:07:51','1');

And viola, I can create multiple locations for a single storage node as long as I give each location a different CIDR value:

MariaDB [fog]> select * from location;
+-----+--------+-------+-----------------+----------------+-------------+------------+---------------------+--------------+
| lID | lName  | lDesc | lStorageGroupID | lStorageNodeID | lCidr       | lCreatedBy | lCreatedTime        | lTftpEnabled |
+-----+--------+-------+-----------------+----------------+-------------+------------+---------------------+--------------+
|   3 | Floor2 | None  |               1 |              1 | 10.0.1.0/24 | wayne      | 2017-12-31 15:07:51 | 1            |
|   4 | Floor1 | None  |               1 |              1 | 10.0.2.0/24 | wayne      | 2017-12-31 15:07:51 | 1            |
+-----+--------+-------+-----------------+----------------+-------------+------------+---------------------+--------------+
2 rows in set (0.00 sec)

The above method I think would involve the least amount of work. It’s not normalized (but the entire fog database is not normalized already). The longer harder way would be to create a table just for CIDRs, and then create a Cidr-location-association table - which would require another screen for adding & associating them and would be more work. Not worth it to go that harder route IMO.

@Lee-Rowlett said:

sourceforge site is down atm (SVN) and is out of our control however rest assured git is the latest version, if unsure just run git pull.

the version detail will be back in the gui if you install SVN Version, when it’s back up.

“SF.net Operations
‏@sfnet_ops
#SourceForge down due to storage platform bug, working 24x7 on recovery and data validation, service restoral. Slashdot restored”

I absolutely love how they keep changing the name of what’s the issue… Yesterday it was “instability” and now it’s a “bug”. lol. SF people, please fix your issue so I can continue with my FOG Updates, Thank you.

@Jbob going into the wiki.

@jeffzimmm Thank you for being co-operative in troubleshooting with us and providing us with ample information in order to assist! This thread should stand as a role-model of how troubleshooting here should happen.

+1s for all your posts here.